Vulnerability Development mailing list archives
Re: History Files
From: jen () ETTNET SE (Joel Eriksson)
Date: Mon, 17 Apr 2000 12:35:19 +0200
On Sun, Apr 16, 2000 at 12:07:02PM -0700, Mark Rafn wrote:
From a pure-technical end, even if you could find a way to keep them from telling bash to log to a "safe" place, they can always do while :; do read x; eval $x; done and bash will not log what that loop does. If you want to do this right, do it with a sniffer.
Nah, what about encryption? You're using SSH, right? :-) Patching the daemons or shells to work as a multiplexer of all input/output is the right way to go (except for when users transfers programs to the box, executes them and erases them of course).
-- Mark Rafn dagon () dagon net <http://www.dagon.net/> !G
-- Joel Eriksson
Current thread:
- Re: History Files, (continued)
- Re: History Files Omachonu Ogali (Apr 15)
- Re: History Files Corwin J. Grey (Apr 15)
- Re: History Files Corwin J. Grey (Apr 15)
- Re: History Files Omachonu Ogali (Apr 15)
- Re: History Files Corwin J. Grey (Apr 15)
- Re: History Files Gert-Jan Hagenaars (Apr 16)
- Re: History Files Bluefish (Apr 17)
- Re: History Files Omachonu Ogali (Apr 15)
- Re: History Files Omachonu Ogali (Apr 15)
- Re: History Files Michael Jennings (Apr 15)
- Re: History Files Mark Rafn (Apr 16)
- Alternative to historyfile logging. Joel Eriksson (Apr 17)
- Re: History Files Joel Eriksson (Apr 17)
- Re: History Files spiff (Apr 18)
- Re: History Files Corwin J. Grey (Apr 16)
- Re: History Files Michael Jennings (Apr 16)
- Cooments on the dvwssr.dll vulnerability threads Iván Arce (Apr 17)
- Re: History Files Senior Systems Administrator - Kris W. (Apr 16)
- quick dirty and most of all-easy process accounting via lkm Security Team (Apr 16)
- Re: History Files George Dodd (Apr 18)
- Re: History Files Perly (Apr 19)
- Re: History Files joyce (Apr 19)