Security Basics mailing list archives
Re: bash_history to track users
From: jrd () gerdesas com
Date: Fri, 14 Nov 2003 14:02:31 -0600 (CST)
Perhaps I am missing something here, but wouldn't modifying bash to syslog the activities be a little more secure in the long run? Especially if re-directing syslog entries to an external syslog server and not keeping them on the local, shell accessible boxes. It would also not be much more difficult then just logging to files. John In previous mail, Sebastian Hans spouted...
--3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Jack Whitsitt (jofny) wrote:The ONLY thing this would useful for is being able to backtrack a clue=-less user. Amalicious 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.=20 That's not entirely accurate. It's fairly easy to modify bash to log this=file elsewhere...andit should not be much harder to have it log to two locations with differe=nt permissions... 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. Seb --=20 /~\ 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 --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/tKkvaRCrClrtHm0RAkVHAJ9YYIAbwUes2kSm3W35p/3HUrmO3QCgit5b 7utsy394lfZ9pKXhp/9Ebhw= =sbeK -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz--
--------------------------------------------------------------------------- Forum Systems PRESIDIO: PGP / XML GATEWAY APPLIANCE The Presidio integrates PGP data encryption and XML Web Services security to simplify the management and deployment of PGP and reduce overall PGP costs by up to 80%. FREE WHITEPAPER & 30 Day Trial - http://www.securityfocus.com/sponsor/ForumSystems_security-basics_031027 ----------------------------------------------------------------------------
Current thread:
- Re: bash_history to track users, (continued)
- Re: bash_history to track users Helder Miguel Rodrigues (Nov 06)
- Re: bash_history to track users Todd Neal (Nov 06)
- Re: bash_history to track users Steve Chadsey (Nov 06)
- Re: bash_history to track users Meritt James (Nov 07)
- Re: bash_history to track users Jimi Thompson (Nov 11)
- Re: bash_history to track users Jack Whitsitt (jofny) (Nov 13)
- Re: bash_history to track users Joe Szilagyi (Nov 14)
- Re: bash_history to track users Sebastian Hans (Nov 17)
- RE: bash_history to track users arek (Nov 14)
- Re: bash_history to track users Sebastian Hans (Nov 14)
- Re: bash_history to track users jrd (Nov 16)
- Re: bash_history to track users Sebastian Hans (Nov 17)
- Re: bash_history to track users Ansgar -59cobalt- Wiechers (Nov 17)
- Re: bash_history to track users Jack Whitsitt (jofny) (Nov 13)
- RE: bash_history to track users Thiago Lima (Nov 16)
- Re: bash_history to track users Sebastian Hans (Nov 17)
- Re: bash_history to track users Helder Miguel Rodrigues (Nov 06)