| 1 |
El jue, 09-01-2014 a las 21:58 +0100, Magnus Granberg escribió: |
| 2 |
> Hi |
| 3 |
> |
| 4 |
> Some time ago we discussed that we should enable stack smashing |
| 5 |
> (-fstack-protector) by default. So we opened a bug to track this [1]. |
| 6 |
> The affected Gcc version will be 4.8.2 and newer. Only amd64, x86, mips, ppc, |
| 7 |
> ppc64 and arm will be affected by this change. |
| 8 |
> |
| 9 |
> You can turn off ssp by using the nossp USE flag or by adding |
| 10 |
> -fno-stack-protector to the CFLAGS and/or CXXFLAGS. We are using the same |
| 11 |
> patch as Debian/Ubuntu but with some Gentoo fixes. |
| 12 |
> |
| 13 |
> The patch will move the sed for the HARD_CFLAGS, ALLCFLAGS and |
| 14 |
> ALLCXXFLAGS from do_gcc_PIE_patches() to make_gcc_hard(). We will |
| 15 |
> make_gcc_hard() the default for all Gcc versions 4.8 and newer, and turn |
| 16 |
> it on or off with hardened_gcc_works() that will make some sanity checks. |
| 17 |
> |
| 18 |
> /Magnus |
| 19 |
|
| 20 |
What are the advantages of disabling SSP to deserve that "special" |
| 21 |
handling via USE flag or easily disabling it appending the flag? |
| 22 |
|
| 23 |
Thanks a lot for the info :) |
Archives