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: <396556a20807181922t32c05b86l335de10bd1106ab2@mail.gmail.com>
Date:	Fri, 18 Jul 2008 19:22:35 -0700
From:	"Adam Langley" <agl@...erialviolet.org>
To:	"YOSHIFUJI Hideaki / 吉藤英明" 
	<yoshfuji@...ux-ipv6.org>
Cc:	netdev@...r.kernel.org
Subject: Re: [RFC 2/2] TCP: Add TCP-AO support

On Fri, Jul 18, 2008 at 6:28 PM, YOSHIFUJI Hideaki / 吉藤英明
<yoshfuji@...ux-ipv6.org> wrote:
> Again, is it okay to add/del one key per each operation?

Yes, I believe so. (At least I can't think of a situation where it isn't)

> If yes, we do not need to change current API too much.

I think, if we're only supporting two keys, the API in the patch (save
making the flags wider etc) is good.

If the concenous is that we need to support > 2 keys per address, then
I'll have a think.


AGL

-- 
Adam Langley agl@...erialviolet.org http://www.imperialviolet.org

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ