Hi,
I've found a bug in the way the kernel handles the PaX flags when
loading an ELF binary.
-- kern/exec_elf.c --
#if defined(PAX_MPROTECT) || defined(PAX_SEGVGUARD) || defined(PAX_ASLR)
l-l_proc-p_pax = epp-ep_pax_flags;
#endif /*
In article 54edb259.7020...@m00nbsd.net,
Maxime Villard m...@m00nbsd.net wrote:
Attached is a patch. However I have a doubt: if the kernel loads a
binary, and then its interpreter, the p_pax flag is not used when load-
ing this interpreter, right?
I don't see why it can't... Try turning it on.
Le 25/02/2015 15:48, Christos Zoulas a écrit :
In article 54edb259.7020...@m00nbsd.net,
Maxime Villard m...@m00nbsd.net wrote:
Attached is a patch. However I have a doubt: if the kernel loads a
binary, and then its interpreter, the p_pax flag is not used when load-
ing this interpreter,
On Feb 25, 4:50pm, m...@m00nbsd.net (Maxime Villard) wrote:
-- Subject: Re: PaX: Heritage bug
| Attached is a patch. However I have a doubt: if the kernel loads a
| binary, and then its interpreter, the p_pax flag is not used when load-
| ing this interpreter, right?
|
| I don't see why it
Le 25/02/2015 18:16, Christos Zoulas a écrit :
On Feb 25, 4:50pm, m...@m00nbsd.net (Maxime Villard) wrote:
-- Subject: Re: PaX: Heritage bug
| Attached is a patch. However I have a doubt: if the kernel loads a
| binary, and then its interpreter, the p_pax flag is not used when load-
|
Anyway I updated my patches; they're based on latest -current.
Changes since the previous are:
- Remove an unexpected contribution comment from kern_dtrace.c
(thanks riastradh!)
- Don't unload systrace.kmod when there are users using dtrace
- Add created from line to *_systrace_args.c
