|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: User's .bash_history
From: Hal Flynn (flynn
SECURITYFOCUS.COM)Date: Sun Oct 01 2000 - 13:10:33 CDT
- Next message: Daniel P. Zepeda: "Re: User's .bash_history"
- Previous message: argoSJG.EDU.EE: "Re: Unbeatable bash! :)"
- Maybe reply: Hal Flynn: "Re: User's .bash_history"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
This thread is definately getting a little old. I'll begin accepting
submissions for a summary post now. Imminent death of this thread is
tonight (US EST).
Hal
> Let's try to sum this up and forget about it please.=20
>
> 1. There are various and sundry ways to lock .bash_history.
> 2. All of the various methods can be got around, depending on the
> cluefulness of the users on the system.=20
> 3. The only way to really reliably monitor user's activity is to use
> kernel-space tools.=20
- Next message: Daniel P. Zepeda: "Re: User's .bash_history"
- Previous message: argoSJG.EDU.EE: "Re: Unbeatable bash! :)"
- Maybe reply: Hal Flynn: "Re: User's .bash_history"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]