Red Hat Bugzilla – Bug 229142
[SECURITY] Does not drop supplementary groups
Last modified: 2009-01-09 02:04:45 EST
Description of problem:
ss5 uses setuid() + setgid() in a wrong way and does not drop supplementary
groups. Please see upstream report at
for more details and suggested fixes.
Version-Release number of selected component (if applicable):
After applying this code, some users got this problem:
ss5 3.6.2 fails to start within a chroot jail
on Linux Fedora Core 6, unlike a previous
ss5 3.4 build.
The error message 3.6.2 produces is:
[ERRO] User nobody not found.
Even with using the -u flag to set the user to
the invoking user I still can't start ss5.
Apparently this is new code in 3.6.2 that wasn't
in 3.4. The offending call appears to be the
call to initgroups() which may not work within
the chroot jail.
I have a workaround which involves #ifdef'ing
the S5UIDSet() call in SS5Main.c since I already
have the UID/GID that I want, but it would be
very handy to figure out why this doesn't work
within a chroot jail. At the least having an
option to ignore the initgroups() return would
be useful for this case.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
f8 has still affected ss5-3.5.9-4
thanks for the update!
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.