All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Harald Welte <laforge@netfilter.org>
Cc: Don Cohen <don-netf@isis.cs3-inc.com>,
	netfilter-devel@lists.netfilter.org, netdev@oss.sgi.com
Subject: Re: Possible ip_defrag DoS ?
Date: Sun, 16 Feb 2003 21:26:04 +0100	[thread overview]
Message-ID: <3E4FF3DC.7090408@trash.net> (raw)
In-Reply-To: <20030216201154.GA30787@sunbeam.de.gnumonks.org>

Harald Welte wrote:

>On Sun, Feb 16, 2003 at 01:38:56PM +0100, Patrick McHardy wrote:
>
>  
>
>>inerestingly, it seems linux defragmentation is vulnerable to dos attack.
>>the evictor (called before defragmentation) just kills the oldest entry
>>of each hash slot, starting with 0 until memory is below
>>sysctl_ipfrag_low_thresh. by sending enough fragments 
>>(>sysctl_ipfrag_high_thresh) which hash to the highest bucket you can
>>stop reassembly of valid packets.
>>    
>>
>
>I'm forwarding this (from netfilter-devel) to the linux networking
>developers at netdev@oss.sgi.com.  If your assumption is valid, they
>might want to have a look at this...
>
>thanks.
>
>
>  
>
Hi Harald, it seems this was not (entirely) correct, the evictor only 
kills the last
member of each hash slot and then moves on. still, assuming the hash 
function is good
there is a good chance we can disturb reassembly noticeable.

Patrick

  reply	other threads:[~2003-02-16 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030215232635.25928.78900.Mailman@kashyyyk>
2003-02-16  1:43 ` [RFC]: ip_conntrack breaks UDP PMTU (Patrick McHardy) Don Cohen
2003-02-16  3:41   ` Patrick McHardy
2003-02-16  6:00     ` Don Cohen
2003-02-16 12:38       ` Patrick McHardy
2003-02-16 20:11         ` Possible ip_defrag DoS ? Harald Welte
2003-02-16 20:26           ` Patrick McHardy [this message]
2003-02-16 20:31           ` Patrick McHardy
2003-02-16 20:01   ` [RFC]: ip_conntrack breaks UDP PMTU (Patrick McHardy) Harald Welte
2003-02-17  9:14     ` Jozsef Kadlecsik
2003-02-17 22:08       ` Don Cohen

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=3E4FF3DC.7090408@trash.net \
    --to=kaber@trash.net \
    --cc=don-netf@isis.cs3-inc.com \
    --cc=laforge@netfilter.org \
    --cc=netdev@oss.sgi.com \
    --cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.