From: Nix <nix@esperi.org.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Emmanuel Fleury <emmanuel.fleury@labri.fr>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to enable/disable security features on mmap() ?
Date: Thu, 08 Dec 2005 16:42:55 +0000 [thread overview]
Message-ID: <8764pzv8ts.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <1134056348.2867.76.camel@laptopd505.fenrus.org> (Arjan van de Ven's message of "8 Dec 2005 15:39:50 -0000")
On 8 Dec 2005, Arjan van de Ven yowled:
>> Moreover, the libc location (and all other dynamic libs) is not
>> randomized under x86_64. I have no explanation for this. :-/
>
> see above; in addition prelink may be interfering with this.
Indeed; prelinked stuff is not randomized. If you want both, prelink
with -R gives the same benefits as ASLR of the shared library location,
pretty much (obviously the libraries have the same address in every
process --- that's kind of the point --- but what that address is is
randomly selected at prelink time).
Prelinking should not affect stack layout randomization.
--
`Don't confuse the shark with the remoras.' --- Rob Landley
next prev parent reply other threads:[~2005-12-08 16:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 14:10 How to enable/disable security features on mmap() ? Emmanuel Fleury
2005-12-08 14:14 ` Arjan van de Ven
2005-12-08 14:21 ` Emmanuel Fleury
2005-12-08 14:39 ` Emmanuel Fleury
2005-12-08 14:49 ` Arjan van de Ven
2005-12-08 14:54 ` Emmanuel Fleury
2005-12-08 15:02 ` Emmanuel Fleury
2005-12-08 15:16 ` linux-os (Dick Johnson)
2005-12-08 15:29 ` Emmanuel Fleury
2005-12-08 15:39 ` Arjan van de Ven
2005-12-08 16:42 ` Nix [this message]
2005-12-08 15:37 ` Arjan van de Ven
2005-12-08 16:08 ` linux-os (Dick Johnson)
2005-12-08 16:14 ` Arjan van de Ven
2005-12-08 16:24 ` linux-os (Dick Johnson)
2005-12-08 16:35 ` Arjan van de Ven
2005-12-08 16:20 ` Xavier Bestel
2005-12-08 16:21 ` Arjan van de Ven
2005-12-08 16:30 ` linux-os (Dick Johnson)
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=8764pzv8ts.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=arjan@infradead.org \
--cc=emmanuel.fleury@labri.fr \
--cc=linux-kernel@vger.kernel.org \
/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