From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: [PATCH] tcp: sysctl to disable TCP simultaneous connect Date: Thu, 14 Feb 2013 21:30:41 -0800 Message-ID: <87y5eq87pa.fsf@xmission.com> References: <20130207175240.GA12520@www.outflux.net> <20130207103950.662698ea@nehalam.linuxnetplumber.net> Mime-Version: 1.0 Content-Type: text/plain Cc: Stephen Hemminger , LKML , Rob Landley , "David S. Miller" , Alexey Kuznetsov , James Morris , Hideaki YOSHIFUJI , Patrick McHardy , Eric Dumazet , Neil Horman , Yuchung Cheng , Shan Wei , "linux-doc\@vger.kernel.org" , netdev@vger.kernel.org, Willy Tarreau To: Kees Cook Return-path: In-Reply-To: (Kees Cook's message of "Thu, 7 Feb 2013 10:44:02 -0800") Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Kees Cook writes: > The patch would not break it -- it defaults the sysctl to staying enabled. > > If you mean the documentation should be updated, sure, that's easy to do. > > David: I know you aren't a fan of this patch, but I'd like to try to > convince you. :) This leaves the feature enabled and add a toggle for > systems (like Chrome OS) that don't want to risk this DoS at all. > There are so very many other toggle, I don't see why this one would be > a problem to add. Chrome OS has no plans to implement webrtc? Last I had read that support had been added to the release versions of Chrome, and was in the development builds of firefox. I really don't belive that there are many systems that don't intend to run a web browser. Eric