LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk> To: Samium Gromoff <_deepfire@feelingofgreen.ru> Cc: Pavel Machek <pavel@ucw.cz>, Samium Gromoff <_deepfire@feelingofgreen.ru>, Valdis.Kletnieks@vt.edu, David Wagner <daw@cs.berkeley.edu>, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Undo some of the pseudo-security madness Date: Tue, 23 Jan 2007 15:41:27 +0000 [thread overview] Message-ID: <20070123154127.57059632@localhost.localdomain> (raw) In-Reply-To: <87mz4996wg.wl@betelheise.deep.net> > SBCL is the most actively developed open source Common Lisp implementation, > which has an optimising native compiler built in, so it is not an interpreter, > and is, most certainly, not crappy. If it requires MAP_FIXED I would beg to disagree. > 1. cannot serve as a vehicle for exploitation for binaries unmarked > with this flag > 2. serve the application deployment cause -- abolish the need for > application-specific system tweaks > 3. remove the need for the ugly self-reexecution tweak people > needing an absolutely unadulterated memory map have to resort to /now/, > even in a non-setuid case Seems sensible to me. If you specifically need that mapping behaviour and ask for it then it wouldn't be hard to provide. > Please, shrug off that C-esque center-of-the-world attitude, > the fact there are thousand times as many C programmers does not Randomisation has nothing to do with C. In fact from a C perspective the compiler and linker do a lot of work to deal with ELF and loading code at arbitary addresses for dynamic linking and the like, not the user and not as language constructs. Perhaps the Lisp universe should wake up and meet the 1980s 8) Alan
next prev parent reply other threads:[~2007-01-23 15:30 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 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 [this message] 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=20070123154127.57059632@localhost.localdomain \ --to=alan@lxorguk.ukuu.org.uk \ --cc=Valdis.Kletnieks@vt.edu \ --cc=_deepfire@feelingofgreen.ru \ --cc=daw@cs.berkeley.edu \ --cc=linux-kernel@vger.kernel.org \ --cc=pavel@ucw.cz \ /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).