From: ebiederm@xmission•com (Eric W. Biederman)
To: Kees Cook <keescook@chromium•org>
Cc: Stephen Hemminger <stephen@networkplumber•org>,
LKML <linux-kernel@vger•kernel.org>,
Rob Landley <rob@landley•net>,
"David S. Miller" <davem@davemloft•net>,
Alexey Kuznetsov <kuznet@ms2•inr.ac.ru>,
James Morris <jmorris@namei•org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6•org>,
Patrick McHardy <kaber@trash•net>,
Eric Dumazet <edumazet@google•com>,
Neil Horman <nhorman@tuxdriver•com>,
Yuchung Cheng <ycheng@google•com>,
Shan Wei <davidshan@tencent•com>,
"linux-doc\@vger.kernel.org" <linux-doc@vger•kernel.org>,
netdev@vger•kernel.org, Willy Tarreau <w@1wt•eu>
Subject: Re: [PATCH] tcp: sysctl to disable TCP simultaneous connect
Date: Thu, 14 Feb 2013 21:30:41 -0800 [thread overview]
Message-ID: <87y5eq87pa.fsf@xmission.com> (raw)
In-Reply-To: <CAGXu5jJiupzommJYPEYQnk-4i9FUKai0NcPnihLN-QpWV64jtQ@mail.gmail.com> (Kees Cook's message of "Thu, 7 Feb 2013 10:44:02 -0800")
Kees Cook <keescook@chromium•org> 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
next prev parent reply other threads:[~2013-02-15 5:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 17:52 [PATCH] tcp: sysctl to disable TCP simultaneous connect Kees Cook
2013-02-07 18:15 ` David Miller
2013-02-07 18:39 ` Stephen Hemminger
2013-02-07 18:44 ` Kees Cook
2013-02-07 19:29 ` H. Peter Anvin
2013-02-07 19:29 ` David Miller
2013-02-15 5:30 ` Eric W. Biederman [this message]
2013-02-15 6:41 ` Kees Cook
2013-02-15 7:10 ` Eric W. Biederman
2013-02-15 7:55 ` Willy Tarreau
2013-02-15 10:31 ` Eric W. Biederman
2013-02-15 10:47 ` Willy Tarreau
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=87y5eq87pa.fsf@xmission.com \
--to=ebiederm@xmission$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=davidshan@tencent$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=jmorris@namei$(echo .)org \
--cc=kaber@trash$(echo .)net \
--cc=keescook@chromium$(echo .)org \
--cc=kuznet@ms2$(echo .)inr.ac.ru \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nhorman@tuxdriver$(echo .)com \
--cc=rob@landley$(echo .)net \
--cc=stephen@networkplumber$(echo .)org \
--cc=w@1wt$(echo .)eu \
--cc=ycheng@google$(echo .)com \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox