1 |
Alexander Schreiber wrote: |
2 |
> On Thu, Jan 08, 2004 at 06:57:28PM +0100, Daniel Privratsky wrote: |
3 |
> |
4 |
>>Wrong. |
5 |
>> |
6 |
>>1) If you don't receive "destination unreachable" packet, you know |
7 |
>>nothing about the target host yet. This is not perfect-network world. |
8 |
>>There can be other fw/router anywhere in the way, killing this type of |
9 |
>>icmp traffic. |
10 |
>> |
11 |
>>2) It slows scans a lot. |
12 |
> |
13 |
> |
14 |
> Only for people too stupid for doing port scans (a rare defect even |
15 |
> among script kiddies). |
16 |
|
17 |
Hmmm, a little schisophrenic situation. Are we talking about mass scan |
18 |
seeking for live systems in some IP space or directed attack to your |
19 |
specific system? |
20 |
For the first scenario it is some useful protection. No response still |
21 |
means system down, attacker will hardly waste time for detail investigation. |
22 |
For the second scenario, it's useful too. Time out waiting will slow him |
23 |
down. |
24 |
|
25 |
> |
26 |
> |
27 |
>>You can of course do scannig in parallel, but |
28 |
>>don't be surprised, when you find yourself killed with no mercy by IDS, |
29 |
>>after matching SYN threshold. 1000+ syns/sec form IP adress to monitored |
30 |
>>system is sure ban. |
31 |
> |
32 |
> |
33 |
> Cool. Your IDS just banned the IPs of your customers mail-, web- and |
34 |
> proxy-servers. Spoofing IP adresses just to mess with such automatic |
35 |
> systems is easy. |
36 |
Nonsense. Such active-response IDS is primary site protection. It |
37 |
detects incoming SYNs, not outgoing. |
38 |
|
39 |
Regards |
40 |
|
41 |
Dan |
42 |
> |
43 |
> Regards, |
44 |
> Alex. |
45 |
|
46 |
|
47 |
-- |
48 |
gentoo-security@g.o mailing list |