Messages in this thread | | | From | Greaves Tristan TM <> | Subject | RE: [PATCH] ip_fragment.c and related, kernel 2.0.34 - Allows , t eardrop/IP fragmentation logging. | Date | Mon, 21 Sep 1998 10:48:05 +0100 |
| |
Hi Paul,
> -----Original Message----- > From: Paul Rusty Russell [mailto:Paul.Russell@rustcorp.com.au] > Sent: Sunday, September 20, 1998 11:51 AM > To: Kernel Mailing List > Subject: Re: [PATCH] ip_fragment.c and related, kernel 2.0.34 > - Allows , > teardrop/IP fragmentation logging.
> [general ip_fragment.c patch discussion] > As far as I can tell (2.1.121), overlapping fragments are handled > correctly, without logging (teardrop). Oversize fragments (Ping of > Death) are logged with a net_ratelimit() wrap to avoid flooding the > logs.
That's right... I never claimed to have "fixed" any overlapping fragment bugs. I simply patched to allow a kernel-option of logging such attempted attacks.
> Neither is checked on packets not defragmented by the Linux box > (either because CONFIG_IP_ALWAYS_DEFRAG is set, or the packet is > destined for the host itself), so be warned.
Thanks for the information, Paul.
Tris.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |