> yeah. There's one security issue: the 'dont randomize' flag must be > cleared when we cross a protection domain. When for example suid-ing in > exec(). Just checked. It should be already done because ADDR_NO_RANDOMIZE is in PER_CLEAR_ON_SETID which is cleared in exec. -Andi - 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/
- References:
- [PATCH for 2.6.18-rc2] [2/8] i386/x86-64: Don't randomize stack top when no randomization personality is set
- From: "Andi Kleen" <[email protected]>
- Re: [PATCH for 2.6.18-rc2] [2/8] i386/x86-64: Don't randomize stack top when no randomization personality is set
- From: Andi Kleen <[email protected]>
- Re: [PATCH for 2.6.18-rc2] [2/8] i386/x86-64: Don't randomize stack top when no randomization personality is set
- From: Ingo Molnar <[email protected]>
- [PATCH for 2.6.18-rc2] [2/8] i386/x86-64: Don't randomize stack top when no randomization personality is set
- Prev by Date: Re: "Why Reuser 4 still is not in" doc
- Next by Date: Re: [PATCH] reiserfs: fix handling of device names with /'s in them
- Previous by thread: Re: [PATCH for 2.6.18-rc2] [2/8] i386/x86-64: Don't randomize stack top when no randomization personality is set
- Next by thread: [PATCH for 2.6.18-rc2] [3/8] i386/x86-64: Add user_mode checks to profile_pc for oprofile
- Index(es):
 |