Bug 163436 - snmpd fails to start with SELinux targeted enforced
snmpd fails to start with SELinux targeted enforced
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Depends On:
  Show dependency treegraph
Reported: 2005-07-16 11:25 EDT by Razvan Sandu
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: 1.25.4-10.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-15 11:59:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Razvan Sandu 2005-07-16 11:25:00 EDT
Description of problem:
On FC3 + "official" updates, the snmpd daemon fails to start when selinux 
targeted is enforced - this breaks snmp reporting to a distant mrtg server.

snmpd used to work OK on this system until some (automatic) update and 
continues to do so if we do a "setenforce 0".

[root@example ~]# service snmpd start
Starting snmpd: /usr/sbin/snmpd: error while loading shared libraries: 
libbeecrypt.so.6: cannot enable executable stack as shared object requires: 
Permission denied
[root@example ~]#

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

How reproducible:

Steps to Reproduce:
1. Install a full Fedora Core 3 + updates as for July 15th,2005, with SELinux 
policy targeted enforced (as default).
2. Make sure you have a valid /etc/snmp/snmpd.conf file
3. Do a service snmpd start.

Actual results:
snmpd doesn't start when "setenforce 1".
snmpd DO start when "setenforce 0".

Expected results:
snmpd should start when "setenforce 1".

Additional info:
Comment 1 Daniel Walsh 2005-07-19 23:46:17 EDT
execstack -c libbeecrypt.so.6:

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