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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 20 Nov 2015 09:40:53 -0800
From:	Yuchung Cheng <>
To:	David Miller <>
Cc:	netdev <>, Eric Dumazet <>
Subject: Re: [PATCH net 1/2] tcp: disable Fast Open on timeouts after handshake

On Fri, Nov 20, 2015 at 7:52 AM, David Miller <> wrote:
> From: Yuchung Cheng <>
> Date: Wed, 18 Nov 2015 18:17:30 -0800
>> Some middle-boxes black-hole the data after the Fast Open handshake
>> (
>> 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 <>
>> Signed-off-by: Eric Dumazet <>
>> Reported-by: Christoph Paasch <>
> 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?
Great question. I should be more clear in the commit message. The
answer is yes it should be sufficient. The tricky part is
tp->bytes_acked includes data acked in the SYN. Since we don't
remember data size sent in SYN, hence the heuristic.
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists