Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 29 Sep 2014 22:34:20 -0400
From: Chet Ramey <chet.ramey@...e.edu>
To: "Kobrin, Eric" <ekobrin@...mai.com>,
        "dwheeler@...eeler.com" <dwheeler@...eeler.com>
CC: chet.ramey@...e.edu, oss-security <oss-security@...ts.openwall.com>,
        solar <solar@...nwall.com>, lcamtuf <lcamtuf@...edump.cx>,
        fweimer <fweimer@...hat.com>
Subject: Re: Healing the bash fork

On 9/29/14, 6:06 PM, Kobrin, Eric wrote:

> What is the motivation to not store executable code (functions) differently from standard variables?

What would you use for such a store, considering the environment is the
only portable way to pass this information from one process to another in
the general case, and support the current set of use cases?

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@...e.edu    http://cnswww.cns.cwru.edu/~chet/

Powered by blists - more mailing lists

Your e-mail address:

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Powered by Openwall GNU/*/Linux - Powered by OpenVZ