Bug 598444 - net-snmpd fails and dies when configured to run as user
net-snmpd fails and dies when configured to run as user
Status: CLOSED DUPLICATE of bug 578405
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: net-snmp (Show other bugs)
6.0
All Linux
low Severity medium
: rc
: ---
Assigned To: Jan Safranek
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-01 08:20 EDT by bugreports2005
Modified: 2010-06-01 08:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-01 08:24:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description bugreports2005 2010-06-01 08:20:32 EDT
Description of problem:

snmpd fails and dies trying to downgrade its privileges, when ran with the -u and -g options.

Version-Release number of selected component (if applicable):

net-snmp-5.5-12.el6.i686 from RHEL6 Beta 1.

How reproducible:

Always.

Steps to Reproduce:
1. Open /etc/sysconfig/snmpd and set something like this:
   OPTIONS="-LS0-6d -Lf /dev/null -p /var/run/snmpd.pid -u daemon -g daemon"
2. service snmpd restart
3. service snmpd status

Actual results:

snmpd dead but pid file exists
a log entry is made saying "initgroups failed: Operation not permitted"

Expected results:

snmpd running as user "daemon".

Additional info:

I understand that snmpd tries to change the group after having already changed the uid and therefore having lost the privilege to do so. Upstream has fixed this by changing the group first and then the uid (SVN revision 18452).
Comment 1 Jan Safranek 2010-06-01 08:24:25 EDT

*** This bug has been marked as a duplicate of bug 578405 ***
Comment 2 Jan Safranek 2010-06-01 08:35:13 EDT
Thanks for the report! It's good to see someone actually tests the beta and reports problems... even if this one was caught by our QA guys.

Note You need to log in before you can comment on or make changes to this bug.