From: Arjan van de Ven <arjan@infradead.org>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org, ubuntu-hardened@lists.ubuntu.com
Subject: Re: Collecting NX information
Date: Mon, 28 Mar 2005 20:55:20 +0200 [thread overview]
Message-ID: <1112036121.6003.46.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <4248520E.1070602@comcast.net>
On Mon, 2005-03-28 at 13:50 -0500, John Richard Moser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> Arjan van de Ven wrote:
> >>As I understand, PT_GNU_STACK uses a single marking to control whether a
> >>task gets an executable stack and whether ASLR is applied to the
> >>executable.
> >
> >
> > you understand wrongly.
> >
> > PT_GNU_STACK just sets the exec permission for the stack (and the heap
> > now mirrors the stack). Nothing more nothing less.
> >
>
> So then this would be slightly more useful than I had previously
> thought, bringing control over the randomization as well?
actually Linus was really against adding non-related things to this
flag. And I think he is right...
Now.. do you have any examples of when you want a binary marked for no-
randomisation ?? (eg something the setarch flag won't fix/won't be good
enough for)
next prev parent reply other threads:[~2005-03-28 18:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 18:21 John Richard Moser
2005-03-28 18:37 ` Arjan van de Ven
2005-03-28 18:50 ` John Richard Moser
2005-03-28 18:55 ` Arjan van de Ven [this message]
2005-03-28 19:14 ` John Richard Moser
2005-03-28 20:54 ` [ubuntu-hardened] " Brandon Hale
2005-03-28 22:17 ` John Richard Moser
2005-03-29 7:16 ` Arjan van de Ven
2005-03-29 7:53 ` John Richard Moser
2005-03-29 8:09 ` Arjan van de Ven
[not found] ` <424911FF.1080702@comcast.net>
2005-03-29 8:46 ` Arjan van de Ven
[not found] ` <42499C40.5030202@comcast.net>
[not found] ` <1112121756.6282.88.camel@laptopd505.fenrus.org>
[not found] ` <4249A78A.1040407@comcast.net>
2005-03-29 19:34 ` Arjan van de Ven
2005-03-29 20:41 ` John Richard Moser
2005-03-29 8:45 ` John Richard Moser
2005-03-29 8:15 ` John Richard Moser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1112036121.6003.46.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
--cc=ubuntu-hardened@lists.ubuntu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®