netdev - Re: [RFC 2/2] TCP: Add TCP-AO 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] [day] [month] [year] [list]

Message-Id: <20080728.133340.40841332.yoshfuji@linux-ipv6.org>
Date:	Mon, 28 Jul 2008 13:33:40 -0400 (EDT)
From:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
To:	agl@...erialviolet.org
Cc:	netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org
Subject: Re: [RFC 2/2] TCP: Add TCP-AO support

In article <396556a20807251434n300ca24bw833f51dc0a332676@...l.gmail.com> (at Fri, 25 Jul 2008 14:34:00 -0700), "Adam Langley" <agl@...erialviolet.org> says:

> /* struct tcp_auth_op_key - add, delete or replace a key
>  * @tcpak_addr - the address of the host to which this key applies
>  * @tcpak_keynum - the number of this key.
>  * @tcpak_tx_keyid - the keyid of this key on the wire when transmitted
>  * @tcpak_keylen - length of the key, in bytes
>  * @tcpak_key - the key data follows this structure
>  */
> struct tcp_auth_op_key {
> 	struct __kernel_sockaddr_storage	tcpak_addr;
> 	__u16					tcpak_keynum;
> 	__u8					tcpak_tx_keyid;
> 	__u8					tcpak_keylen;
> 	__u8					tcpak_reserved[4];
> 	__u8					tcpak_key[0];
> };

Let's share layout between tcp_md5sig{} and tcp_auth_op_key{} like this:
struct tcp_auth_op_key {
	struct __kernel_sockaddr_storage        tcpak_addr;
	__u16					tcpak_keynum;
	__u16					tcpak_keylen;
	__u8					tcpak_tx_keyid;
	__u8					tcpak_reserved[3];
	__u8					tcpak_key[0];
};

Then we can share TCP_AUTH_KEY_SET and TCP_MD5SIG.

--yoshfuji
--
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