netdev - Re: [PATCH] NET: Add TCP connection abort IOCTL

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070327.185246.41635477.davem@davemloft.net>
Date:	Tue, 27 Mar 2007 18:52:46 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jheffner@....edu
Cc:	mhuth@...sta.com, dagriego@...il.com, davem@...emloft.ne,
	netdev@...r.kernel.org
Subject: Re: [PATCH] NET: Add TCP connection abort IOCTL

From: John Heffner <jheffner@....edu>
Date: Tue, 27 Mar 2007 20:27:44 -0400

> As a concrete example of a way I've used this type of feature is to 
> defend against a netkill [1] style attack, where the defense involves 
> making decisions about which connections to kill when memory gets 
> scarce.  It makes sense to do this with a system daemon, since an admin 
> might have an arbitrarily complicated policy as to which applications 
> and peers have priority for the memory.  This is too complicated to 
> distribute and enforce across all applications.  You could do this in 
> the kernel, but why if you don't have to?

On the contrary this sounds like an excellent task for
a netfilter based solution.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html