| Summary: | www-servers/nginx: denied bad rename of /var/lib/nginx/tmp/fastcgi | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | cyberbat <cyberbat83> |
| Component: | Hardened | Assignee: | The Gentoo Linux Hardened Team <hardened> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | bugs, whissi |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
cyberbat
2015-04-05 12:28:40 UTC
Can you try pax-marking the binary and see if it persists? There seems to be a few flags that might be relevant (GRKERNSEC_CHROOT_RENAME comes to mind). Since I don't have a grsec kernel I'd appreciate if you could try a few different options and let me know what works for you. (In reply to Johan Bergström from comment #1) > Can you try pax-marking the binary and see if it persists? There seems to be > a few flags that might be relevant (GRKERNSEC_CHROOT_RENAME comes to mind). > Since I don't have a grsec kernel I'd appreciate if you could try a few > different options and let me know what works for you. It seems that I can't turn off GRKERNSEC_CHROOT_RENAME for nginx binary using paxctl. Turning sysctl kernel.grsecurity.chroot_deny_bad_rename=0 fix the situation. But it will be much better if nginx don't make such "bad" things. BTW, I've tried nginx 1.8.0 and issue still happens. This is probably something we have to show upstream. Could you please re-test with recent >=www-servers/nginx-1.10.1 if nginx still triggers these warnings? |