Date: Sun, 24 Aug 2008 23:16:58 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: freebsd-arch@freebsd.org Subject: Re: Magic symlinks redux Message-ID: <200808250616.m7P6GwEa055070@apollo.backplane.com> References: <g8kv7v$sp2$1@ger.gmane.org> <20080822150020.GA57443@lor.one-eyed-alien.net> <9bbcef730808220802pa84b597u457100a23b03a80c@mail.gmail.com> <20080822153945.GC57443@lor.one-eyed-alien.net> <9bbcef730808220853q22666b44n5ca2b7add991191f@mail.gmail.com> <48B23A0E.1030700@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
The only issue we hit with per-process varsyms is that to really
be useful the shells need built-ins to set the process-space variables,
since doing so as an exec'd subprocess will not effect the shell or its
children. We have no plans to allow one process to modify another
process's varsyms as that would cause significant security issues.
In fact, even the per-user variables might have security issues
(e.g. common-run 'nobody' user utilities, and so forth, for which
a pseudo-userid has not been created). I'm kinda thinking of removing
per-user variables despite the usefulness.
There have been various circumstances where we've thought varsyms
would be useful, but ended up not needing to use them.
Right now we are looking at possibly using them to point /usr/lib and
friends to select 32 or 64 bit ABI library paths, and have the kernel
automatically set a varsym when exec'ing an ELF program to the
program's ABI. Doing this would allow 32 and 64 bit program, library,
and package sets to be run and maintained side-by-side.
-Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200808250616.m7P6GwEa055070>