| Summary: | milter module does not define any policy for TCP connections | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lubos Stanek <lubek> |
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | dwalsh, mgrepl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | selinux-policy-3.9.7-37.fc14 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-03-21 11:24:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
We have this in F15. I am fixing it in F14 policy. Thank you. Fixed in selinux-policy-3.9.7-34.fc14 selinux-policy-3.9.7-34.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/selinux-policy-3.9.7-34.fc14 Thanks for working on the issue.
The clamav-milter case is fixed.
milter-greylist works both as a server and a client in the peer mode. The list is synchronized among all MX servers (multi-MX).
type=AVC msg=audit(1300464048.285:103): avc: denied { listen } for pid=11719 comm="milter-greylist" lport=5252 scontext=system_u:system_r:greylist_milter_t:s0 tcontext=system_u:system_r:greylist_milter_t:s0 tclass=tcp_socket
Probably this rule should be added:
corenet_tcp_sendrecv_movaz_ssc_port(greylist_milter_t)
Miroslav you need this line from F15 allow greylist_milter_t self:tcp_socket create_stream_socket_perms; selinux-policy-3.9.7-37.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/selinux-policy-3.9.7-37.fc14 The issue is fixed by the last policy (selinux-policy-3.9.7-37.fc14). Thanks for your work. Please update karma selinux-policy-3.9.7-37.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: There is no policy for TCP connections from the milters in the milter module. At least two milters use TCP connections. I have not found any advice or comment regarding milter TCP connections except packaging notes in clamav. clamav-milter can communicate with the clamd server via a TCP socket. And it seems to be the preferred way for Fedora according to the packager's notes. The connection is blocked on localhost by SELinux: type=AVC msg=audit(1298921074.999:229): avc: denied { name_connect } for pid=20406 comm="clamav-milter" dest=3310 scontext=system_u:system_r:clamd_t:s0 tcontext=system_u:object_r:clamd_port_t:s0 tclass=tcp_socket milter-greylist can synchronize lists among multiple MX servers (the peer option). Again there is no policy for the sync connection and the connection is blocked by SELinux: type=AVC msg=audit(1298996484.455:768): avc: denied { name_bind } for pid=15967 comm="milter-greylist" src=5252 scontext=system_u:system_r:greylist_milter_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket I think that the milters' TCP communication support should be included in some form. P.S.: I do not need any help for making it work. Version-Release number of selected component (if applicable): selinux-policy-3.9.7-31.fc14.noarch clamav-milter-0.97-1400.f14..i686 milter-greylist-4.2.6-1400.fc14.i686 How reproducible: Install the mentioned milter. Configure ClamdSocket or peer depending on the installed milter. Start the milter. Actual results: SELinux emits AVCs, milters cannot communicate. Expected results: Milters can use at least the default configuration and communicate.