netdev - Re: [PATCH net 1/2] tcp: disable Fast Open on timeouts after handshake

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: <20151120.105229.472836583674901954.davem@davemloft.net>
Date:	Fri, 20 Nov 2015 10:52:29 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	ycheng@...gle.com
Cc:	netdev@...r.kernel.org, edumazet@...gle.com
Subject: Re: [PATCH net 1/2] tcp: disable Fast Open on timeouts after
 handshake

From: Yuchung Cheng <ycheng@...gle.com>
Date: Wed, 18 Nov 2015 18:17:30 -0800

> Some middle-boxes black-hole the data after the Fast Open handshake
> (https://www.ietf.org/proceedings/94/slides/slides-94-tcpm-13.pdf).
> The exact reason is unknown. The work-around is to disable Fast Open
> temporarily after multiple recurring timeouts with few or no data
> delivered in the established state.
> 
> Signed-off-by: Yuchung Cheng <ycheng@...gle.com>
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
> Reported-by: Christoph Paasch <cpaasch@...le.com>

Applied and queued up for -stable.

Just out of curiosity, why isn't a test for zero data sufficient?

Do these middle-boxes sometimes not black-hole all of the data?
--
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