Bug 444376 - selinux prevents iscsid service shutdown
selinux prevents iscsid service shutdown
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
Depends On:
Blocks: F9Blocker
  Show dependency treegraph
Reported: 2008-04-27 21:30 EDT by Matt Domsch
Modified: 2008-04-28 10:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-28 10:30:36 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 Matt Domsch 2008-04-27 21:30:35 EDT
Description of problem:
run command : /sbin/service iscsid stop.  Note AVC denial:

type=AVC msg=audit(1209345908.152:23): avc:  denied  { signal } for  pid=2485
comm="iscsid" scontext=system_u:system_r:iscsid_t:s0
tcontext=system_u:system_r:iscsid_t:s0 tclass=process
type=SYSCALL msg=audit(1209345908.152:23): arch=c000003e syscall=62 success=no
exit=-13 a0=9b4 a1=f a2=40a788 a3=8101010101010100 items=0 ppid=1 pid=2485
auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
tty=(none) ses=4294967295 comm="iscsid" exe="/sbin/iscsid"
subj=system_u:system_r:iscsid_t:s0 key=(null)

SELinux is preventing iscsid (iscsid_t) "signal" to <Unknown> (iscsid_t).
Detailed Description
SELinux denied access requested by iscsid. It is not expected that this access
is required by iscsid and this access may signal an intrusion attempt. It is
also possible that the specific version or configuration of the application is
causing it to require additional access. 

Version-Release number of selected component (if applicable):
Comment 1 Daniel Walsh 2008-04-28 10:30:36 EDT
You can allow this for now.

# audit2allow -M mypol -l -i /var/log/audit/audit.log
# semodule -i mypol.pp

Fixed in selinux-policy-3.3.1-42.fc9.noarch

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