Hello, i am not sure, if this is really blocking or just logging: Feb 16 14:02:32 mordor setroubleshoot: #012 SELinux hindert /usr/sbin/saslauthd (saslauthd_t) "read" am Zugriff auf <Unknown> (usr_t).#012 For complete SELinux messages. run sealert -l fd56262f-2db7-46cd-9771-7a4fcc546531 Feb 16 14:15:00 mordor setroubleshoot: #012 SELinux hindert /usr/libexec/postfix/smtpd (postfix_smtpd_t) "write" am Zugriff auf <Unknown> (postgrey_spool_t).#012 For complete SELinux messages. run sealert -l 0b218c2c-40b1-4d64-821f-5f1a991157d3 Feb 16 14:15:19 mordor setroubleshoot: #012 SELinux hindert /usr/lib/AntiVir/antivir (amavis_t) "getattr" am Zugriff auf /sys (sysfs_t).#012 For complete SELinux messages. run sealert -l ee5a81fa-7b17-4ffa-8fac-cea3b325a614 Feb 16 14:36:57 mordor setroubleshoot: #012 SELinux hindert /usr/sbin/saslauthd (saslauthd_t) "read" am Zugriff auf <Unknown> (usr_t).#012 For complete SELinux messages. run sealert -l fd56262f-2db7-46cd-9771-7a4fcc546531 Feb 16 15:06:05 mordor setroubleshoot: #012 SELinux hindert /usr/sbin/saslauthd (saslauthd_t) "read" am Zugriff auf <Unknown> (usr_t).#012 For complete SELinux messages. run sealert -l fd56262f-2db7-46cd-9771-7a4fcc546531 Sorry for the german versions, so i can translate all of those in one: setroubleshoot: #012 SELinux stops [application] (xxxx_t) "whatever" access to <Unknown> (usr_t)... the rest of the lines is written in better english than mine. Now the question: i run selinux in permissive-mode, as otherwise i always have dozens of megs of log from aide. I thought, permissive-mode never blocks, just reports. So, now, what is fact? is this blocking or just saying that it is blocking? Thanks for your response. Roger
