Your message dated Fri, 15 Jun 2007 22:59:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#414388: Policy blocks lynx/liblzo via execstack
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: selinux-policy-refpolicy-targeted
Version: 0.0.20061018-5
I'm not sure what the policy is on reporting selinux causing failures of
installed software, or if this should be considered a bug or just
badness with lynx/liblzo instead and a valid reason to block it via
selinux, so this might need reassigned or closed depending.
The selinux-policy-refpolicy-targeted rules block running lynx/liblzo
via execstack protection. E.g., see below:
[EMAIL PROTECTED]:~$ lynx
lynx: error while loading shared libraries: liblzo.so.1: cannot enable
executable stack as shared object requires: Permission denied
[EMAIL PROTECTED]:~$ dmesg | grep lynx | tail -1
audit(1173620260.257:39): avc: denied { execstack } for pid=7548
comm="lynx" scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
--- End Message ---
--- Begin Message ---
This is a duplicate of #336138.
--- End Message ---
