netdev - Re: [RFC] tcp: Add (limited) SYNACK payload support

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: <20080813.210251.47504019.davem@davemloft.net>
Date:	Wed, 13 Aug 2008 21:02:51 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	agl@...erialviolet.org
Cc:	netdev@...r.kernel.org
Subject: Re: [RFC] tcp: Add (limited) SYNACK payload support

From: "Adam Langley" <agl@...erialviolet.org>
Date: Tue, 12 Aug 2008 13:56:47 -0700

> This patch implements the draft spec:
> http://www.ietf.org/internet-drafts/draft-agl-tcpm-sadata-01.txt
> 
> At the moment, this is just an [RFC] patch because an option number hasn't been
> assigned by the IETF yet.
> 
> It allows listening sockets to be configured with a small (<= 64 bytes),
> payload that is included in SYN/ACK packets elicited by SYN packets that
> include a special option. See the draft linked to above for motivations.
> 
> Additionally, the listening socket can request that the kernel replace 8 bytes
> of the payload with random data (that can later be read from the resulting
> accepted socket).

This looks mostly fine to me.  I would even advocate not using a config
option for this.
--
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