Re: bash_history set to zero length
- From: Kevin Bailey <kbaileyremovthis@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 19 Sep 2006 10:31:18 +0100
Ralf Fassel wrote:
* Kevin Bailey <kbaileyremovthis@xxxxxxxxxxxxxxxxxxx>
| BTW - it was only a single bash_history which was empty.
Do you know that it was non-empty any time prior?
E.g., I had my *history files non-writable for some time, so they
always were size 0.
R'
Nope, but I've only just started using chkrootkit on all servers so I would
not have received warnings about zero length bash_history files before.
I will run a big nessus scan on the machine today to look for any unusual
open ports. The logs are still not showing any sign of a compromise.
Kevin
.
- Follow-Ups:
- Re: bash_history set to zero length
- From: responder
- Re: bash_history set to zero length
- References:
- bash_history set to zero length
- From: Kevin Bailey
- Re: bash_history set to zero length
- From: responder
- Re: bash_history set to zero length
- From: Kevin Bailey
- Re: bash_history set to zero length
- From: Ralf Fassel
- bash_history set to zero length
- Prev by Date: Re: bash_history set to zero length
- Next by Date: killing a kernel thread ....... UDP server (kernel module).........
- Previous by thread: Re: bash_history set to zero length
- Next by thread: Re: bash_history set to zero length
- Index(es):