[Buildroot] [PATCHv3] toolchain: granular choice for stack protector
Thomas Petazzoni
thomas.petazzoni at free-electrons.com
Sun Dec 27 11:45:25 UTC 2015
Steven,
On Sun, 27 Dec 2015 03:39:19 -0800, Steven Noonan wrote:
> When SSP is *enabled* (BR2_ENABLE_SSP) the default should be
> BR2_SSP_STRONG (if available). It's generates code that's
> better-protected than BR2_SSP_REGULAR, but faster and smaller than
> BR2_SSP_ALL.
>
> Only crazy folks would use BR2_SSP_ALL if BR2_SSP_STRONG is an option. ;)
We want to preserve existing behavior as much as possible. So people
who enabled BR2_ENABLE_SSP were paying the price of BR2_SSP_ALL, and we
should therefore keep using BR2_SSP_ALL for such users. That's the
point of legacy handling: minimizing the amount of "surprise" /changes
for users upgrading Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
More information about the buildroot
mailing list