Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 68274 - sys-apps/slocate-2.7-r6: slocate installed setuid root
Summary: sys-apps/slocate-2.7-r6: slocate installed setuid root
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Security
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-20 07:27 UTC by Ulrich Müller
Modified: 2011-10-30 22:38 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Müller gentoo-dev 2004-10-20 07:27:50 UTC
/usr/bin/slocate is installed setuid root which is not necessary.
It should be installed setgid slocate as it used to be for -r5.

Besides, there seems to be no ChangeLog entry about this change. :-(
Comment 1 Thierry Carrez (RETIRED) gentoo-dev 2004-10-20 07:32:13 UTC

*** This bug has been marked as a duplicate of 67977 ***
Comment 2 Ulrich Müller gentoo-dev 2004-10-20 07:39:33 UTC
I disagree about this being a duplicate. From the time in the CVS header:

$Header: /var/cvsroot/gentoo-x86/sys-apps/slocate/slocate-2.7-r6.ebuild,v 1.2 
2004/10/18 19:30:42 vapier Exp $

it appears that in the original -r6 v1.1 the setgid bit was lost and the "fix"
of bug 67977 was to install slocate setuid root instead.
Comment 3 Sven Wegener gentoo-dev 2004-10-20 07:41:44 UTC
No, this is not a dup. vapier messed the ebuild up by setting go-r,a+s which sets suid and sgid. And created no ChangeLog entry. I just fixed the ebuild.
Comment 4 Thierry Carrez (RETIRED) gentoo-dev 2004-10-20 07:59:45 UTC
Sorry about this
Comment 5 Thierry Carrez (RETIRED) gentoo-dev 2004-10-20 08:02:32 UTC
Blame vapier
As problem was only temporary and only affected a ~ package, no GLSA is needed.

swegener: be sure to revbump (if not already done) so that people having installed the bad ebuild will catch the new one at the next update.