On Thu, Aug 30, 2012 at 04:29:26PM -0600, Theo de Raadt wrote:
> > On Wed, Aug 29, 2012 at 11:16 AM, Matthew Dempsky
> > wrote:
> > > First, make sure you're using a reasonably up to date snapshot.
> > > You're up to date if "nm /usr/lib/crtbegin.o" mentions __guard_local.
> >
> > At least two p
> On Wed, Aug 29, 2012 at 11:16 AM, Matthew Dempsky wrote:
> > First, make sure you're using a reasonably up to date snapshot.
> > You're up to date if "nm /usr/lib/crtbegin.o" mentions __guard_local.
>
> At least two people have commented that the snapshots they downloaded
> don't have __guard_l
On Wed, Aug 29, 2012 at 11:16 AM, Matthew Dempsky wrote:
> First, make sure you're using a reasonably up to date snapshot.
> You're up to date if "nm /usr/lib/crtbegin.o" mentions __guard_local.
At least two people have commented that the snapshots they downloaded
don't have __guard_local yet. H
Just pinging this again since I've only received one test report so
far, and this really needs more testing on architectures other than
just amd64. alpha and hppa don't have -fstack-protector, so really
that means arm, i386, mips, powerpc, sh, and sparc64. Please please
please test if you have on
First, make sure you're using a reasonably up to date snapshot.
You're up to date if "nm /usr/lib/crtbegin.o" mentions __guard_local.
Next, apply the patch below to GCC, recompile, and install:
$ cd /usr/src/gnu/gcc/gcc
$ patch < /path/to/diff
$ cd /usr/src/gnu/usr.bin/cc
$ make depend &&
