grsecurity (never mind!)

Has anyone been able to get a kernel to boot in pvgrub with the grescurity patches applied? I've been fighting with it for a day or so and it won't work…I'm using a Linode 360 with Gentoo. I first tried the gentoo-hardened kernel (which includes both grsecurity and SELinux) with the pvops options enabled…when I tried to boot, it hung with no console output.

Then I tried the 2.6.27.4-linode14 sources and the config that is used when that kernel is selected on the Dashboard. Without applying any patches, I was at least able to get that kernel to compile and boot. I used incremental patches to upgrade to 2.6.27.10 (the kernel version grsecurity patches against), and it still booted. Then I applied the grsecurity patch, compiled (no config changes), and the kernel pagefaulted immediately. Obviously, after that, I didn't try enabling grsecurity or PaX in the kernel config.

Has anyone gotten this to work? Any ideas how?

1 Reply

Update: It works if I start with linux-2.6.27.4-x86_64-linode3 as the base for patching. Had I done some more extensive googling, I'd have discovered that grsecurity in general has issues with 32-bit kernels. :oops:

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct