This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: randomized stack protector value

From: Jakub Jelinek <jakub at redhat dot com>
To: Kees Cook <kees at canonical dot com>
Cc: Ulrich Drepper <drepper at redhat dot com>, libc-alpha at sourceware dot org
Date: Thu, 2 Oct 2008 00:09:48 +0200
Subject: Re: randomized stack protector value
References: <20081001201116.GD12527@outflux.net> <48E3EFD6.2010704@redhat.com> <20081001215657.GH12527@outflux.net>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Wed, Oct 01, 2008 at 02:56:57PM -0700, Kees Cook wrote:
> On Wed, Oct 01, 2008 at 02:47:02PM -0700, Ulrich Drepper wrote:
> > Kees Cook wrote:
> > > What would be needed to help get this approved?
> > 
> > The patch will never be in cvs, it's a hack.
> 
> Heh.  I realize it's not in cvs for a reason, but I was hoping to start
> a discussion on how to best solve the need it addresses, in a way that
> would be acceptable to the glibc maintainers.

The right solution is that the kernel provides a couple of random words
in the auxiliary vectors.  Some kernel folks know about this for quite some
time, but it hasn't been added yet.  If kernel provides it, upstream
glibc will most definitely use it.

	Jakub

Follow-Ups:
- Re: randomized stack protector value
  - From: Roland McGrath

References:
- randomized stack protector value
  - From: Kees Cook
- Re: randomized stack protector value
  - From: Ulrich Drepper
- Re: randomized stack protector value
  - From: Kees Cook

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]