From: Paul Sebastian Ziegler <psz@observed.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Did I just get hacked???
Date: Mon, 12 Feb 2007 07:02:25 +0100 [thread overview]
Message-ID: <45D002F1.5060404@observed.de> (raw)
In-Reply-To: <49bf44f10702111631q757afb4x865b48e7bbffdb62@mail.gmail.com>
Hi Grant,
personally (but this is by far only ONE possible setup for your task)
I'd advise you to connect eth0 to wan through a box set up as a bridge
(try brctl). If that box has a good wireless card and good drivers (this
mostly means "if that box isn't running Windows") you can also put that
wireless-card into promiscuous mode lock it to your chanel and ssid and
feed wireshark your WEP-Key or WPA-PSK for decryption.
If not, then you'll have to use a second box for the wireless sniffing.
BTW. current rootkits won't just replace ps or some other tools. Good
rootkits do not run in userspace; they run in kernelspace. They directly
intercept the function-calls. Just another thing to keep in mind while
trying to scan for them.
hth
Paul
Grant schrieb:
>> > A good rootkit will install a "ps" that won't show the 'bot
>> > processes. The one time a machine of mine got hacked, netstat
>> > still worked, but I don't know why a hacked netstat couldn't be
>> > installed as well.
>>
>> > Looking through /proc/≤pid> is probably still reliable.
>>
>>
>> Hello Grant,
>>
>> I keep an old portable around, running wireshark and a flat hub.
>> You can set your ethernet address to 0.0.0.0 and fire up wireshark.
>>
>> You can then sniff any (ethernet) segment of your network for
>> nefarious traffic or male-configured network applictions.
>
> Ok, it sounds like the key to figuring this out is watching the
> outgoing network traffic for weird stuff. eth0 is on the WAN and
> wireless ath0 is on the local subnet. How would you monitor the
> outgoing traffic considering my setup?
>
> - Grant
> │ИМ╒▀╛z╦\x1e·з(╒╦&j)b· bst==
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-02-12 6:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 2:27 [gentoo-user] Did I just get hacked??? Grant
2007-02-11 3:06 ` Jerry McBride
2007-02-11 4:11 ` Grant
2007-02-11 3:38 ` Albert Hopkins
2007-02-11 4:06 ` Chris Nolan
2007-02-11 4:29 ` [gentoo-user] " Grant Edwards
2007-02-11 21:16 ` James
2007-02-12 0:31 ` Grant
2007-02-12 6:02 ` Paul Sebastian Ziegler [this message]
2007-02-12 13:30 ` Shawn Singh
2007-02-12 13:35 ` Shawn Singh
2007-02-12 3:58 ` Grant
2007-02-12 15:32 ` Dan Farrell
2007-02-12 16:33 ` Willie Wong
2007-02-12 18:05 ` Grant
2007-02-13 8:07 ` nicolas.cornu
2007-02-22 23:34 ` [gentoo-user] " Grant
2007-02-23 0:51 ` Neil Bothwick
2007-02-23 17:48 ` Andrey Gerasimenko
2007-02-23 18:47 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45D002F1.5060404@observed.de \
--to=psz@observed.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox