linux-kernel - Re: strange Mac OSX RST behavior

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: <20160701191609.1fc1c045@lxorguk.ukuu.org.uk>
Date:	Fri, 1 Jul 2016 19:16:09 +0100
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Jason Baron <jbaron@...mai.com>
Cc:	Rick Jones <rick.jones2@....com>, <linux-kernel@...r.kernel.org>,
	<netdev@...r.kernel.org>, <davem@...emloft.net>,
	<eric.dumazet@...il.com>
Subject: Re: strange Mac OSX RST behavior

> yes, we do in fact see a POLLRDHUP from the FIN in this case and
> read of zero, but we still have more data to write to the socket, and
> b/c the RST is dropped here, the socket stays in TIME_WAIT until
> things eventually time out...

After the FIN when you send/retransmit your next segment do you then get
a valid RST back from the Mac end?

Alan