On 2/1/15 1:52 AM, Jonathan Hankins wrote:
> ​Right. My concern is that a potential exploit could inject a malicious
> value for HISTFILE into the environment. I think (but may be wrong) that
> HISTFILE is the only codepath in a default shell invocation that could
> result in a silent writing to an arbitrary file without direct action on
> the part of the user.
If I can inject arbitrary variables into the environment, I'm not going to
mess around with HISTFILE. I'm going straight to LD_PRELOAD or maybe
LD_LIBRARY_PATH, game over.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
