Re: how to find trace of attacks
- To: debian-user@lists.debian.org
- Subject: Re: how to find trace of attacks
- From: Andrei Popescu <andreimpopescu@gmail.com>
- Date: Thu, 1 Jan 2009 13:03:38 +0200
- Message-id: <[🔎] 20090101110338.GO5606@think.homelan>
- In-reply-to: <c956da920812311257l1bf982f3m93f03511a02b8dc0@mail.gmail.com>
- References: <46688cb90812292324h1d2779dcs5982fd30393b45cd@mail.gmail.com> <880dece00812310157m6883c58di174b272fc09b7c31@mail.gmail.com> <495B657F.9040606@gmail.com> <20081231145026.GC4132@blitz.hooton> <495BA910.60601@gmail.com> <c956da920812311257l1bf982f3m93f03511a02b8dc0@mail.gmail.com>
On Wed,31.Dec.08, 15:57:14, Jeff Soules wrote:
> If you know where you'll be sshing in from, you can use iptables to
> deny access to the appropriate port with MAC filtering and possibly IP
> range rules.
This won't work because MACs are used only on the local[1] segment.
[1] local in my case would be between the laptop and my AP
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
Attachment:
signature.asc
Description: Digital signature
Reply to: