Runtime change to LD_LIBRARY_PATH

[Ken Whaley]

Sounds like a potential security problem if a program is able to
change out the LD_LIBRARY_PATH in mid-execution to affect future
loads without the user's knowledge.

Ken


> -----Original Message-----
> From: libc-alpha-owner@sources.redhat.com
> [ mailto:libc-alpha-owner@sources.redhat.com]On Behalf Of Ed Connell
> Sent: Friday, August 17, 2001 11:32 AM
> To: 'libc-alpha@sources.redhat.com'
> Subject: Runtime change to LD_LIBRARY_PATH
> 
> 
> I noticed that if you set LD_LIBRARY_PATH after your program 
> is running, ld.so does not take that into account when trying 
> to resolve future dlopen's.  (_dl_init_paths() sets 
> env_path_list while ld.so is initializing and it is left 
> alone after that.)  It would be easy to check LD_LIBRARY_PATH
> for changes each time you want to map a new object.  Would 
> that be rational change to make?  I'll code it up if people
> like the idea.
> 
> Thanks
> Ed
>