netdev - Re: [PATCH v3 1/7] Only parse time stamp TCP option in time wait sock

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4AE5D4AE.2080108@gmail.com>
Date:	Mon, 26 Oct 2009 12:56:14 -0400
From:	William Allen Simpson <william.allen.simpson@...il.com>
To:	Gilad Ben-Yossef <gilad@...efidence.com>
CC:	netdev@...r.kernel.org, ori@...sleep.com,
	Yony Amit <yony@...sleep.com>
Subject: Re: [PATCH v3 1/7] Only parse time stamp TCP option in time wait
 sock

Gilad Ben-Yossef wrote:
> Since we only use tcp_parse_options here to check for the exietence
> of TCP timestamp option in the header, it is better to call with
> the "established" flag on.
> 
Please explain how this patch is required for the other patches?

And more importantly, why it is better to call with established on?

And most importantly, what end cases you considered, and how this
interacts with the proposed rfc1323bis changes, especially on reset?
--
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