How to ignore LD_LIBRARY_PATH

[Stephen John Smoogen]

On Tue, Aug 23, 2011 at 11:44, Orion Poplawski <orion at cora.nwra.com> wrote:
> See https://bugzilla.redhat.com/show_bug.cgi?id=719785 for the motivation
>
> The environment module system allows users to modify their environment in a
> predictable way, including setting LD_LIBRARY_PATH.  However, this makes it
> possible to break the modulecmd binary by putting an incompatible TCL (or
> other) library earlier in the path.  It would be great if modulecmd were made
> impervious to such things, but I don't know the best or acceptable method to
> do this.  I'm guessing using rpaths would be the easiest.
>
> Thoughts/suggestions?
>

To be honest, I think this falls under: User shoots self in foot. I
have run into this a lot and done it quite a few times myself... but
in the end it usually meant finding out I had old software I no longer
needed while not breaking software I still needed to have work. Is
this a security issue?


-- 
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Let us be kind, one to another, for most of us are fighting a hard
battle." -- Ian MacLaren