Description of problem: SELinux is preventing /usr/libexec/dovecot/imap-login from using the 'execstack' accesses on a process. ***** Plugin catchall (100. confidence) suggests ************************** If vous pensez que imap-login devrait être autorisé à accéder execstack sur les processus étiquetés dovecot_t par défaut. Then vous devriez rapporter ceci en tant qu'anomalie. Vous pouvez générer un module de stratégie local pour autoriser cet accès. Do autoriser cet accès pour le moment en exécutant : # grep imap-login /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:dovecot_t:s0 Target Context system_u:system_r:dovecot_t:s0 Target Objects [ process ] Source imap-login Source Path /usr/libexec/dovecot/imap-login Port <Unknown> Host (removed) Source RPM Packages dovecot-2.2.9-1.fc21.x86_64 Target RPM Packages Policy RPM selinux-policy-3.13.1-10.fc21.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.13.0-0.rc3.git5.1.fc21.x86_64 #1 SMP Sat Dec 14 15:06:01 UTC 2013 x86_64 x86_64 Alert Count 1 First Seen 2013-12-30 11:11:42 CET Last Seen 2013-12-30 11:11:42 CET Local ID c2c2e00b-b62a-4a5e-8421-aa58bfba9ee2 Raw Audit Messages type=AVC msg=audit(1388398302.370:81949): avc: denied { execstack } for pid=29763 comm="imap-login" scontext=system_u:system_r:dovecot_t:s0 tcontext=system_u:system_r:dovecot_t:s0 tclass=process type=SYSCALL msg=audit(1388398302.370:81949): arch=x86_64 syscall=mprotect success=no exit=EACCES a0=7fff57fd1000 a1=1000 a2=1000007 a3=0 items=0 ppid=921 pid=29763 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=imap-login exe=/usr/libexec/dovecot/imap-login subj=system_u:system_r:dovecot_t:s0 key=(null) Hash: imap-login,dovecot_t,dovecot_t,process,execstack Additional info: reporter: libreport-2.1.10 hashmarkername: setroubleshoot kernel: 3.13.0-0.rc3.git5.1.fc21.x86_64 type: libreport
*** This bug has been marked as a duplicate of bug 1045699 ***