netdev - Re: [RFC PATCH 0/3] Make rfc3686 template work with asynchronous block ciphers

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: <20121228.152311.290755667605168896.davem@davemloft.net>
Date:	Fri, 28 Dec 2012 15:23:11 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	herbert@...dor.apana.org.au
Cc:	jussi.kivilinna@...et.fi, linux-crypto@...r.kernel.org,
	steffen.klassert@...unet.com, netdev@...r.kernel.org
Subject: Re: [RFC PATCH 0/3] Make rfc3686 template work with asynchronous
 block ciphers

From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Sat, 29 Dec 2012 09:42:49 +1100

> On Fri, Dec 28, 2012 at 12:04:48PM +0200, Jussi Kivilinna wrote:
>> I'm not sure how this patchset should be dealt with (should 1st patch go
>> through different tree than 2nd and 3rd?), so therefore it's RFC.
>> 
>> Second patch makes rfc3686 template work with asynchronous block ciphers and
>> third patch changes aesni-intel to use this template. First patch fixed problem
>> in xfrm_algo found with help of 2nd and 3rd patches and without 1st patch
>> 2nd patch breaks aes-ctr with IPSEC.
> 
> I think the easiest way is to have these patches go through Dave's
> tree.

Better yet, Steffen's IPSEC tree :-)
--
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