On Fri, Jul 24, 2009 at 01:54:04PM +0200, Jeremie Le Hen wrote: > On Fri, Jul 24, 2009 at 11:18:42AM +0300, Kostik Belousov wrote: > > On Fri, Jul 24, 2009 at 09:34:51AM +0200, Jeremie Le Hen wrote: > > > Hi Ed, > > > > > > Sorry for the late reply. > > > > > > On Sat, May 09, 2009 at 02:13:13PM +0200, Ed Schouten wrote: > > > > We probably could. I think I discussed this with Robert Watson some time > > > > ago and we could use things like ELF hints. But still, that doesn't > > > > prevent us from reaching this limitation later on. > > > > > > Can you elaborate a little? Are you talking about elf-hints.h? > > > I don't see where we can get randomness from it. > > > > The thing is called ELF auxillary information vector. It is used to > > supply some useful information for interpreter from the kernel, > > see include/machine/elf.h for AT_* entries. > > Ah ok, so the idea is to generate a new hint, for instance AT_RANDOM, > generated at link time, that will be used to fill the canary at exec(2) > time? The aux entries are not hints, and they are put on the new image stack when execve() activates the image. Aux entries has nothing to do with static link time, they are supplied to the dynamic linker (ELF interpreter).
pgpFY5GAPaI2S.pgp
Description: PGP signature
