On Sat, Jul 30, 2011 at 9:11 AM, Lisa Kachold wrote:
> Larry,
>
> Let's define rootkit: The name for a kit of hacker utilities placed on
> a UNIX machine after a successful compromise. A typical rootkit
> includes: password sniffer log cleaners replacement binaries for
> common programs on the sys
Doesn't "rootkit" sound like something a dentist would have around the
office?
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/li
Larry,
Let's define rootkit: The name for a kit of hacker utilities placed on
a UNIX machine after a successful compromise. A typical rootkit
includes: password sniffer log cleaners replacement binaries for
common programs on the system (e.g. inetd) backdoor programs
replacements to programs like
> search example.com
> nameserver 1.2.3.4
> nameserver 5.6.7.8
>
>
dig crow202.org 1.2.3.4>> 131 ms response
dig crow202.org 5.6.7.8>> 75 ms response
I'd never heard of the dig command before, and both seems to have use the
8.8.8.8 nameserver. I was hoping to check each nameserver this wa
Thanks Joseph,
Even where I had some idea what most of those things were you added to what
I knew about them. For example, it was obvious some of those files were
Pulse Audio stuff, but I had no idea the /dev/shm/ files were interfaces to
shared memory.
On the other hand, I still wonder why the
