
tazok.id0 at gmail
May 17, 2010, 8:19 PM
Post #7 of 10
(995 views)
Permalink
|
|
Re: Re: Hardened meeting summary 2010-05-16
[In reply to]
|
|
AFAIK FORTIFY_SOURCE only works in fixed size buffers. To me ssp is a more complete (and slightly different) approach, while FORTIFY_SOURCE checks the existence of a buffer overflow directly, ssp does it by checking the modification of the canary (indirect approach) but could get applied with any kind of code since it's not limited to fixed size buffers. SSP to me is really necessary http://www.trl.ibm.com/projects/security/ssp/ http://gcc.gnu.org/ml/gcc-patches/2004-09/msg02055.html 2010/5/18 Peter Hjalmarsson <xake [at] rymdraket> > > > I would say you're worrying too much. > > The important part in the toolchain equation is really PIE (and of > course -z,now, relro and those other stuff people forgets about) to give > you ASLR, and it is there in hardened gcc-4.3 in tree. SSP is also there > to some extent because it is implemented in FORTIFY_SOURCE which is > enabled in all of gentoo by default. > So I would say that the extra part SSP from GCC is nice but not > necessary. > > Regards > Peter > > > >
|