netdev - Re: Fw: [Bug 93901] New: TCP Fast Open uses

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: <54EF5EE0.7040404@hp.com>
Date:	Thu, 26 Feb 2015 09:58:56 -0800
From:	Rick Jones <rick.jones2@...com>
To:	Eric Dumazet <eric.dumazet@...il.com>,
	Stephen Hemminger <stephen@...workplumber.org>
CC:	netdev@...r.kernel.org, Yuchung Cheng <ycheng@...gle.com>,
	rueth@...sys.rwth-aachen.de
Subject: Re: Fw: [Bug 93901] New: TCP Fast Open uses

On 02/26/2015 08:13 AM, Eric Dumazet wrote:
> This is work in progress at Google, of course.
>
> Classic chicken and egg problem ;)

Does it need to be any more complicated than a sysctl which enables 
accepting an alternate (the experimental) option value in addition to 
the assigned, to be enabled (perhaps by default for a release or three) 
for the server side, and then just switching the active connection 
establishment side to the assigned number?

If the server is "old" and using the experimental version, the only 
thing that will happen is the clients using the standardized version 
will end-up falling back on the classic three-way handshake.  That 
doesn't seem so bad.  Particularly since that option value was 
"experimental" after all and presumably then not really meant for 
"production" purposes :)

rick jones

--
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