> > You need to consider that in the end I'd need PT_GNU_STACK to do > everything PaX wants why? Why not have independent flags for independent things? That way you have both cleanness of design and you don't break anything. > The point is > to not break anything, yet to still make things easier for those > projects and distributions like Hardened Ubuntu. to achieve that you need to get the toolchain to omit this stuff automatically somehow. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [ubuntu-hardened] Re: Collecting NX information
- From: John Richard Moser <[email protected]>
- Re: [ubuntu-hardened] Re: Collecting NX information
- From: John Richard Moser <[email protected]>
- Re: [ubuntu-hardened] Re: Collecting NX information
- References:
- Collecting NX information
- From: John Richard Moser <[email protected]>
- Re: Collecting NX information
- From: Arjan van de Ven <[email protected]>
- Re: Collecting NX information
- From: John Richard Moser <[email protected]>
- Re: Collecting NX information
- From: Arjan van de Ven <[email protected]>
- Re: Collecting NX information
- From: John Richard Moser <[email protected]>
- Re: [ubuntu-hardened] Re: Collecting NX information
- From: Brandon Hale <[email protected]>
- Re: [ubuntu-hardened] Re: Collecting NX information
- From: John Richard Moser <[email protected]>
- Collecting NX information
- Prev by Date: [PATCH] Reduce stack usage in module.c
- Next by Date: Re: [PATCH] typo fix in drivers/scsi/sata_svw.c
- Previous by thread: Re: [ubuntu-hardened] Re: Collecting NX information
- Next by thread: Re: [ubuntu-hardened] Re: Collecting NX information
- Index(es):
 |