netdev - Re: [PATCH 01/11] rxrpc: Add a common object cache

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: <20160308.151311.928321529565045584.davem@davemloft.net>
Date:	Tue, 08 Mar 2016 15:13:11 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	dhowells@...hat.com
Cc:	linux-afs@...ts.infradead.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/11] rxrpc: Add a common object cache

From: David Howells <dhowells@...hat.com>
Date: Tue, 08 Mar 2016 11:39:57 +0000

> One could argue, I suppose, that things should've been arranged that the RxRPC
> client would manage the lifetime of each connection it sets up, rather than
> both ends letting it lapse by mutual loss of interest.  But you *still* have to
> have a timeout, lest the client die and not close its connection.

But the point is if there is no limitation on the number of these connections
that can be setup.... wait for troubles.

And if you try to put in some kind of limit to handle this, it's then
easy for the bad guy to block out other legitimate users.