On Fri, 5 Mar 2004, Sasha Pachev wrote:
> Being hacked is a possibility, and it could have happened in conjuction with
> something else, but I doubt that hacking alone with give you the panic. Most
> hackers are not very interested in destroying your data per say unless you
> tick them off - they just want to control the box. And even if they feel
> destructive, rm -rf / or dd if=/dev/zero of=/dev/hda makes a lot more sense
> and requires a lot less work than introducing a weird problem into the
> kernel.
The logs he quoted indicate a breakin almost certainly. Kernel errors could
be a side-effect of the original hack or later, poorly designed measures.
I really like that he wants to track down what the original break was, but I'm
not coming up with too many ways of doing that after the fact. Seems like the
best we could do would be to do forensics on the current state of the machine
- what binaries have changed and whatnot. But that doesn't necessarily have
any bearing on the original attack.
I don't suppose you ever ran tripwire on that machine?
-J
____________________
BYU Unix Users Group
http://uug.byu.edu/
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list