| 1 |
SSP is stack smashing protection. Unless an application your using for |
| 2 |
some strange reason likes to over run the stack and execute code just |
| 3 |
like a buffer overrun attack you won't have a problem. As far as Quake3 |
| 4 |
goes you won't have a problem with the hardened tool chain. |
| 5 |
|
| 6 |
John Schember |
| 7 |
|
| 8 |
|
| 9 |
On Sat, 2007-01-27 at 18:20 -0800, gentoo-hardened-ml-01@××××××.org |
| 10 |
wrote: |
| 11 |
> I've had a "partially-hardened" workstation for awhile now. I use |
| 12 |
> hardened-sources and enable many of the PaX/grsecurity options including |
| 13 |
> stack smashing protection. This works great as I can disable SEGMEXEC, |
| 14 |
> PAGEEXEC and mprotect for Quake3 (ioquake3) and get it to run. My question |
| 15 |
> is if I take my workstation to a full hardened system with SSP+PIE toolchain, |
| 16 |
> etc. will I still be able to run Quake3 and other programs like it? If I |
| 17 |
> went to a full Hardened Gentoo system, even if I disabled PaX's SEGMEXEC, |
| 18 |
> PAGEXEC and mprotect, which is sufficient to run Quake3 now, the toolchains' |
| 19 |
> own SSP would then kick in and stop me, right? |
| 20 |
> |
| 21 |
> I'm normally a test and do-it-myself kind of person, but I really don't want |
| 22 |
> to have to recompile the system to find out and then recompile again if gcc's |
| 23 |
> SSP/ProPolice does stop me. |
| 24 |
> |
| 25 |
> Side note: I masked gcc-4* and >=glibc-2.4 when they were stabled in x86. I |
| 26 |
> still run gcc-3.4.6-r2 and glibc-2.3.6-r5 so switching to the hardened |
| 27 |
> profile will not present any of those types of problems for me. |
| 28 |
> |
| 29 |
> Thank you for your help. |
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-hardened@g.o mailing list |
Archives