Bug 163436

Summary: snmpd fails to start with SELinux targeted enforced
Product: [Fedora] Fedora Reporter: Razvan Sandu <rsandu>
Component: selinux-policy-targetedAssignee: Daniel Walsh <dwalsh>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: rsandu
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: 1.25.4-10.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-15 15:59:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Razvan Sandu 2005-07-16 15:25:00 UTC
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
                                                           [FAILED]
[root@example ~]#


Version-Release number of selected component (if applicable):
selinux-policy-targeted-1.17.30-3.16
beecrypt-3.1.0-6 
net-snmp-5.2.1.2-FC3.1


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-20 03:46:17 UTC
execstack -c libbeecrypt.so.6: