grsecurity forums

my patch was just a rediff of the beta 1.9.12 patch against 2.4.22-rc2. Afaik no new features were adding to the final 1.9.12 so just copying the .config should work just fine. You might want to use make oldconfig to doublecheck.

copying the config didn't work, (i didn't think to do make oldconfig-- i figured it wouldn't be necessary since versions were almost exactly the same) and even a new config didn't work. same problem. that's why i wanted to try your patch, before i even give an attempt at troubleshooting this problem i'm going to try your patch to try to isolate the problem.. that is if you still have it or it's still accessible somewhere.

no sorry, i deleted it from both my hdd and the server. The difference between the 2 patches can't be the problem though. I applied grsec 1.9.12 to a vanilla 2.4.22 tree and it works with all possible configs afaik. Make sure you've got support for SHA256 in the cryptographic API options though.
If it still does not work you might want to post a link you your .config or an error message.

Sleight of Mind wrote:no sorry, i deleted it from both my hdd and the server. The difference between the 2 patches can't be the problem though. I applied grsec 1.9.12 to a vanilla 2.4.22 tree and it works with all possible configs afaik. Make sure you've got support for SHA256 in the cryptographic API options though.
If it still does not work you might want to post a link you your .config or an error message.

ok, that may be the problem. i don't remember enabling it the first time, but perhaps i changed something and didn't realize it. the config that won't work has the cryptographic api enabled, but none of its options are enabled. i'm re-compiling with sha256 enabled now-- thanks. you people have been extremely helpful.

ok well to let you know that solved the problem. and then the server hard drive died. but the kernel booted beforehand