> > > >I picture this somehow as being just a bit more > functionality added to mprotect(2): > > > >/* following magic to identify operating on that > segment, rather than > > * a particular address > > */ > >#define ADDR_STACK (void *) (-1) > >#define ADDR_HEAP (void *) (-2) > > > >mprotect(ADDR_STACK, 0, > (PROT_READ|PROT_WRITE|PROT_EXEC)); > > It's a bit harder to bolt on the current > implementation of the > stack protection. And what is the "ADDR_STACK" *all* > current > thread stacks, the stack of main or the current > stack?
Which does the PT_SUNWSTACK header apply to? I'm not sure what point there would be in per-thread control; if any one thread in an address space is exploitable, the whole address space is potentially corruptible. -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
