| Summary: | =app-antivirus/clamav-0.97 denied RWX mmap on /usr/sbin/clamd | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
| Component: | Current packages | Assignee: | Net-Mail Packages <net-mail+disabled> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | andreis.vinogradovs, antivirus, hardened, mjo |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Agostino Sarubbo
2011-07-28 13:25:43 UTC
clamd use JIT compilation for rules in startup time; Also, clamd verify PAX kernel in debug mode, i.e: clamd --debug LibClamAV Warning: Bytecode: disabling JIT because PaX is preventing 'mprotect' access. Run 'paxctl -cm <executable>' Please add call paxctl in ebuild in hardened profile. Also see http://git.clamav.net/gitweb?p=clamav-bytecode-compiler.git;a=patch;h=2706b400bf598278ec6e0817c1b544bfad3d28c2 these binares should be PAX'ed: /usr/sbin/clamd /usr/bin/clamscan /usr/bin/clamconf Since this bug is still open... Here's what happens when I start clamd: # /etc/init.d/clamd start LibClamAV Warning: RWX mapping denied: Can't allocate RWX Memory: Operation not permitted LibClamAV Warning: RWX mapping denied: Can't allocate RWX Memory: Operation not permitted LibClamAV Warning: RWX mapping denied: Can't allocate RWX Memory: Operation not permitted LibClamAV Warning: RWX mapping denied: Can't allocate RWX Memory: Operation not permitted LibClamAV Warning: RWX mapping denied: Can't allocate RWX Memory: Operation not permitted * Starting clamd ... LibClamAV Warning: RWX mapping denied: Can't allocate RWX Memory: Operation not permitted LibClamAV Warning: Bytecode: disabling JIT because PaX is preventing 'mprotect' access. Run 'paxctl -cm <executable>' Certainly this looks bad (and the suggestion is wrong these days, it should be to use paxctl-ng). If Anthony's comment on bug #326199 is true, can we at least hide the warnings? Maybe upstream would be willing to change the message to say something like "Falling back to interpreted bytecode..." or whatever. If there's a one-to-one correspondence between the "RWX mapping denied" warnings and the JIT fallback, the former shouldn't be displayed if the latter is. It would make this a lot less frightening. is this still happening with current (stable/unstable) version? putting RESOLVED-NEEDINFO please just re-open if it is still a problem. |