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 the 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 file elsewhere...and
it should not be much harder to have it log to two locations with
This makes the discussion a little bit more interesting..
Without hacking the code, though, I suppose you can write a
script to parse the output of "w"
and have it add items as they change.
What kind of an environment are you trying to secure - is this a
business where you can use something like a key stroke logger?
or is it open to the