Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 119366
| Summary: | Syslog is not able to log to remote server under SELinux. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Konstantin Ryabitsev <icon> |
| Component: | policy | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | leonard-rh-bugzilla |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | triage|leonardjo|closed|rawhide | ||
| Fixed In Version: | 1.11.3-2 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-05-10 17:45:03 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 122683 | ||
Adding the following to
/etc/security/selinux/src/policy/domains/program/syslogd.te fixes the
issue and allows both sending logs to remote server and accepting
remote logs.
# Allow name_bind for remote logging
allow syslogd_t port_t:{ tcp_socket udp_socket } name_bind;
tcp_socket can be used by syslog_ng, afair.
Fixed in policy-1.11.3-2.src.rpm |
Description of problem: SELinux enforcement disables remote server logging for syslog, creating the following entries in messages: Mar 29 13:25:56 hagrid kernel: audit(1080584756.667:0): avc: denied { name_bind } for pid=3162 exe=/sbin/syslogd src=832 scontext=root:system_r:syslogd_t tcontext=system_u:object_r:port_t tclass=udp_socket It looks like the default policy should allow this, as remote logging is used quite often. Version-Release number of selected component (if applicable): sysklogd-1.4.1-14