|
From: | David Sugar |
Subject: | [Bayonne-devel] Bayonne::Libexec in cpan, and separated libexec for 0.7.0 |
Date: | Mon, 25 Jul 2005 08:43:16 -0400 |
User-agent: | Mozilla Thunderbird 1.0.5 (Macintosh/20050711) |
In 0.7.0, which will probably get released after I return from Chicago, the libexec system is now a fully isolated process which is exec'd from libexec.bin. This was done for two primary reasons:
First, as a matter of security, this assures there is no bayonne image code present when executing an embedded interpreter. Hence, no information is leaked through memory.
Second, the libexec process now does not have lots of extra things mapped into it, or even C++ related dependencies, inherited from Bayonne. This assures that when embedded interpreter libraries are added to libexec they do not appear in, and as embeded interpreters execute, they have no chance to interfere with, the running Bayonne image.
dyfet.vcf
Description: Vcard
[Prev in Thread] | Current Thread | [Next in Thread] |