LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Samium Gromoff <_deepfire@feelingofgreen.ru> To: Florian Weimer <fw@deneb.enyo.de> Cc: Samium Gromoff <_deepfire@feelingofgreen.ru>, Kyle Moffett <mrmacman_g4@mac.com>, David Wagner <daw-usenet@taverner.cs.berkeley.edu>, LKML Kernel <linux-kernel@vger.kernel.org> Subject: Re: [PATCH] Undo some of the pseudo-security madness Date: Sat, 24 Feb 2007 16:33:53 +0300 [thread overview] Message-ID: <87irdrbry6.wl@betelheise.deep.net> (raw) In-Reply-To: <87k5y799lo.fsf@mid.deneb.enyo.de> At Sat, 24 Feb 2007 10:40:51 +0100, Florian Weimer wrote: > > * Samium Gromoff: > > > Lisp environments can produce standalone executables > > If you've got a stand-alone executable, you don't need MAP_FIXED. The > ELF loader maps the program at a fixed address anyway (at least on > i386 and x86_64, I haven't checked others). Not so. The thing is that the picture is of two pieces: - the executable - the unrelocatable lisp core (which is unrelocatable by the virtue of non-PIC code) which is mapped into the AS of the executable. It is the latter which breaks, as its map can overlap with randomized pieces of the executable (along with its libraries). > AFAIK, PolyML has recently made the switch to stand-alone executables > for this reason. regards, Samium Gromoff
next prev parent reply other threads:[~2007-02-24 13:34 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-21 23:23 [PATCH] Undo some of the pseudo-security madness Samium Gromoff 2007-01-21 23:34 ` David Wagner 2007-01-22 0:36 ` Kyle Moffett 2007-01-22 1:53 ` Samium Gromoff 2007-02-24 9:40 ` Florian Weimer 2007-02-24 13:33 ` Samium Gromoff [this message] 2007-02-24 13:49 ` Florian Weimer 2007-01-22 15:20 ` Valdis.Kletnieks 2007-01-22 17:39 ` Samium Gromoff 2007-01-23 8:48 ` Pavel Machek 2007-01-23 14:03 ` Samium Gromoff 2007-01-23 15:41 ` Alan 2007-01-23 20:21 ` [PATCH 0/2] Mechanism to turn of ASR on a per-ELF binary basis Samium Gromoff 2007-01-23 20:28 ` [PATCH 1/2] Define the EF_AS_NO_RANDOM e_flag bit Samium Gromoff 2007-01-23 20:50 ` Jakub Jelinek 2007-01-23 21:06 ` Samium Gromoff 2007-01-23 21:16 ` Jakub Jelinek 2007-01-23 21:54 ` Samium Gromoff 2007-01-23 23:21 ` Samium Gromoff 2007-01-24 17:08 ` Pavel Machek 2007-01-29 1:18 ` Arjan van de Ven 2007-01-23 20:31 ` [PATCH 2/2] Make the EF_AS_NO_RANDOM e_flag bit disable PF_RANDOMIZE Samium Gromoff 2007-02-24 9:51 ` [PATCH] Undo some of the pseudo-security madness Florian Weimer 2007-02-24 13:36 ` Samium Gromoff 2007-01-31 9:59 ` Arjan van de Ven 2007-02-01 8:05 ` Florian Weimer -- strict thread matches above, loose matches on Subject: below -- 2007-01-22 0:54 Samium Gromoff 2007-01-20 14:37 Samium Gromoff 2007-01-20 16:12 ` Samium Gromoff 2007-01-20 21:58 ` David Wagner 2007-01-21 2:16 ` Arjan van de Ven 2007-01-21 21:38 ` Samium Gromoff 2007-01-21 22:09 ` Samium Gromoff 2007-01-21 22:16 ` David Wagner 2007-01-22 0:35 ` Arjan van de Ven 2007-01-22 1:15 ` Samium Gromoff 2007-01-22 17:52 ` Samium Gromoff 2007-01-23 8:44 ` Pavel Machek
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=87irdrbry6.wl@betelheise.deep.net \ --to=_deepfire@feelingofgreen.ru \ --cc=daw-usenet@taverner.cs.berkeley.edu \ --cc=fw@deneb.enyo.de \ --cc=linux-kernel@vger.kernel.org \ --cc=mrmacman_g4@mac.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: linkBe 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; as well as URLs for NNTP newsgroup(s).