Description of problem: systemctl start postgrey SELinux is preventing postgrey from 'read' accesses on the file unix. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that postgrey should be allowed read access on the unix file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'postgrey' --raw | audit2allow -M my-postgrey # semodule -X 300 -i my-postgrey.pp Additional Information: Source Context system_u:system_r:postgrey_t:s0 Target Context system_u:object_r:proc_net_t:s0 Target Objects unix [ file ] Source postgrey Source Path postgrey Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-3.14.5-39.fc32.noarch Local Policy RPM selinux-policy-targeted-3.14.5-39.fc32.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.6.14-300.fc32.x86_64 #1 SMP Wed May 20 20:47:32 UTC 2020 x86_64 x86_64 Alert Count 1 First Seen 2020-06-18 10:17:10 EDT Last Seen 2020-06-18 10:17:10 EDT Local ID 9e02af4c-5df5-4156-801d-100e0c84da73 Raw Audit Messages type=AVC msg=audit(1592489830.909:1330356): avc: denied { read } for pid=2206417 comm="postgrey" name="unix" dev="proc" ino=4026532057 scontext=system_u:system_r:postgrey_t:s0 tcontext=system_u:object_r:proc_net_t:s0 tclass=file permissive=0 Hash: postgrey,postgrey_t,proc_net_t,file,read Version-Release number of selected component: selinux-policy-targeted-3.14.5-39.fc32.noarch Additional info: component: selinux-policy reporter: libreport-2.13.1 hashmarkername: setroubleshoot kernel: 5.6.14-300.fc32.x86_64 type: libreport
Similar problem has been detected: systemctl start postgrey hashmarkername: setroubleshoot kernel: 5.6.15-300.fc32.x86_64 package: selinux-policy-targeted-3.14.5-39.fc32.noarch reason: SELinux is preventing postgrey from 'read' accesses on the file unix. type: libreport
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.