RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1460479 - /usr/bin/newaliases.sendmail and /usr/sbin/sendmail.sendmail try to access sysctl_net_t
Summary: /usr/bin/newaliases.sendmail and /usr/sbin/sendmail.sendmail try to access sy...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-11 01:04 UTC by Robert Scheck
Modified: 2019-08-13 15:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-13 15:04:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Robert Scheck 2017-06-11 01:04:45 UTC 
Description of problem:
type=AVC msg=audit(1495146039.669:299): avc:  denied  { search } for  pid=9038 comm="newaliases" name="net" dev="proc" ino=9469 scontext=unconfined_u:unconfined_r:system_mail_t:s0-s0:c0.c1023 tcontext=system_u:object_r:sysctl_net_t:s0 tclass=dir
type=SYSCALL msg=audit(1495146039.669:299): arch=c000003e syscall=2 success=no exit=-13 a0=7f5fe86074b0 a1=80000 a2=1b6 a3=24 items=0 ppid=9036 pid=9038 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=51 sgid=51 fsgid=51 tty=pts1 ses=3 comm="newaliases" exe="/usr/sbin/sendmail.sendmail" subj=unconfined_u:unconfined_r:system_mail_t:s0-s0:c0.c1023 key=(null)

type=AVC msg=audit(1497081381.192:1576): avc:  denied  { search } for  pid=18875 comm="sendmail" name="net" dev="proc" ino=90465 scontext=system_u:system_r:sendmail_t:s0 tcontext=system_u:object_r:sysctl_net_t:s0 tclass=dir
type=SYSCALL msg=audit(1497081381.192:1576): arch=c000003e syscall=2 success=no exit=-13 a0=7f8038ce14b0 a1=80000 a2=1b6 a3=24 items=0 ppid=1 pid=18875 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=51 sgid=51 fsgid=51 tty=(none) ses=4294967295 comm="sendmail" exe="/usr/sbin/sendmail.sendmail" subj=system_u:system_r:sendmail_t:s0 key=(null)

Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-102.el7_3.16.noarch
sendmail-8.14.7-4.el7.x86_64

How reproducible:
Everytime, see above and below. Basically a system with GUI and sendmail.

Actual results:
/usr/bin/newaliases.sendmail and /usr/sbin/sendmail.sendmail try to access 
sysctl_net_t.

Expected results:
No AVC denied, but I have no idea if that should be allowed or not.
Comment 5 Zdenek Pytela 2019-08-13 15:04:12 UTC 
The requested permissions seem to have already been present in the current version as a result of other implemented changes, hence closing CURRENTRELEASE.
Note You need to log in before you can comment on or make changes to this bug.