Content-Type: text/plain; charset=us-ascii
Jack Whitsitt (jofny) wrote:
The ONLY thing this would useful for is being able to backtrack a clue=
-less user. A
malicious user with clue will do what he wants and then go hand edit t=
he bash history.
After all, it's in his home
directory and he owns it.
That's not entirely accurate. It's fairly easy to modify bash to log this=
it should not be much harder to have it log to two locations with differe=
But not too different. The user must still have write access. Otherwise,
how would the shell write to it? If the shell can write to it, so can
the user. Anyway, what if the user has more than one instance running?
=2Ebash_history only has the history of one instance. Or tcsh? Or any
other shell for that matter?
Without hacking the code, though, I suppose you can write a script to par=
se the output of "w"
and have it add items as they change.
But this only catches
(1) the foreground process, not processes running in the background
(you could parse the output of ps instead) and
(2) processes that are running while you are doing the w (or ps). Some
could slip through.
/~\ The ASCII Sebastian Hans
\ / Ribbon Campaign hanss () in tum de
X Against HTML 0x5AED1E6D
/ \ Email! 014C 4A54 FED4 C0B5 3E87 427B 6910 AB0A 5AED 1E6D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
-----END PGP SIGNATURE-----