Subject: Re: RFC: migration to a fully dynamically linked system
To: NetBSD Userlevel Technical Discussion List <tech-userlevel@NetBSD.ORG>
From: Todd Vierling <firstname.lastname@example.org>
Date: 12/23/2001 11:28:46
On Fri, 21 Dec 2001, Greg A. Woods wrote:
: > 2. There are times when it is useful for a program, whether statically
: > or dynamically linked itself, to (optionally) load pieces of code, etc.
: > from shared objects. This is the functionality currently provided to
: > dynamically linked programs by dlopen(), but missing in statically
: > linked programs.
: I do not agree. Any program which really needs the ability to load,
: even optionally, any additional code after having started, can always be
: dynamically linked. This is the only way to even come close to
: preserving the integrity of the unix process security model.
s/can always be/must always be/
Making dlopen() "work" in static binaries is basically asking the ELF spec
to bend itself over a table....
-- Todd Vierling <email@example.com> * Wasabi & NetBSD: Run with it.
-- CDs, Integration, Embedding, Support -- http://www.wasabisystems.com/