Bug#503173: set correct PAX flags with paxctl as package default on i386 and amd64

2011-02-23 Thread Pierre Ynard
GRUB uses nested functions and so requires an executable stack. Sorry. Okay, then the best is to have PAX_EMUTRAMP support in the kernel and use paxctl -cE on the concerned binaries. I wrote a patch that does that when building the package; maybe it's needed for the other binaries that I haven't

Bug#609602: Bug#503173: set correct PAX flags with paxctl as package default on i386 and amd64

2011-02-16 Thread Colin Watson
On Wed, Feb 16, 2011 at 03:12:43AM +, Pierre Ynard wrote: Now with version 1.99, I also have to run an additional: paxctl -cpsm /usr/bin/grub-script-check What does grub do that needs to by-pass PaX restrictions? Is it specific to x86? GRUB uses nested functions and so requires an

Bug#503173: set correct PAX flags with paxctl as package default on i386 and amd64

2011-02-15 Thread Pierre Ynard
merge 503173 609602 thanks Now with version 1.99, I also have to run an additional: paxctl -cpsm /usr/bin/grub-script-check What does grub do that needs to by-pass PaX restrictions? Is it specific to x86? -- Pierre Ynard -- To UNSUBSCRIBE, email to

Bug#503173: set correct PAX flags with paxctl as package default on i386 and amd64

2011-01-17 Thread Christoph Scheurer
Hello, I also regularly fix this problem (bugs 609602,503173) by setting the required PAX flags on the respective grub binaries from grub-common and grub-pc with paxctl: paxctl -cpsm /usr/sbin/grub-setup paxctl -cpsm /usr/sbin/grub-mkdevicemap paxctl -cpsm /usr/sbin/grub-probe It