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: Roland McGrath <roland at redhat dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Kees Cook <kees at canonical dot com>, Ulrich Drepper <drepper at redhat dot com>, libc-alpha at sourceware dot org
Date: Wed, 1 Oct 2008 15:27:06 -0700 (PDT)
Subject: Re: randomized stack protector value
References: <20081001201116.GD12527@outflux.net><48E3EFD6.2010704@redhat.com><20081001215657.GH12527@outflux.net><20081001220948.GC32107@sunsite.ms.mff.cuni.cz>

> 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.

Sounds easy enough.  How many?  Do you want:

	{AT_RANDOM1, x}
	{AT_RANDOM2, y}

giving 8 bytes on 32-bit and 16 on 64-bit?

Or perhaps:

	{AT_RANDOM, a}
	{AT_RANDOM_SIZE, p}

where a is the address (on the initial stack near auxv) of p random bytes?
Then what should p be in the initial implementation?


Thanks,
Roland

Follow-Ups:
- Re: randomized stack protector value
  - From: Kees Cook
- [PATCH] ELF: implement AT_RANDOM for future glibc use
  - From: Kees Cook

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

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