Re: [PATCH] tcp: sysctl to disable TCP simultaneous connect
From: Eric W. Biederman
Date: Fri Feb 15 2013 - 02:11:24 EST
Kees Cook <keescook@xxxxxxxxxxxx> writes:
> On Thu, Feb 14, 2013 at 9:30 PM, Eric W. Biederman
> <ebiederm@xxxxxxxxxxxx> wrote:
>> Kees Cook <keescook@xxxxxxxxxxxx> 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.
> I haven't looked at the internals of webrtc. Are you implying some
> feature in it relies on the TCP simultaneous connect?
I am saying that yes.
webrtc is built on ICE (interactivity connectivity establishment). ICE
support for TCP (RFC6544) uses TCP simultaneous connect. webrtc
supports tcp connections.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/