Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-27 Thread Milan Broz
On 27/06/2019 09:42, Ard Biesheuvel wrote: > On Wed, 26 Jun 2019 at 23:11, Samuel Neves wrote: >> >> , On Wed, Jun 26, 2019 at 8:40 AM Milan Broz wrote: >>> >>> On 26/06/2019 09:15, Ard Biesheuvel wrote: >>> Thanks for the insight. So I guess we have consensus that MORUS should be remov

Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-27 Thread Ard Biesheuvel
On Wed, 26 Jun 2019 at 23:11, Samuel Neves wrote: > > , On Wed, Jun 26, 2019 at 8:40 AM Milan Broz wrote: > > > > On 26/06/2019 09:15, Ard Biesheuvel wrote: > > > > > Thanks for the insight. So I guess we have consensus that MORUS should > > > be removed. How about aegis128l and aegis256, which h

Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-26 Thread Samuel Neves
, On Wed, Jun 26, 2019 at 8:40 AM Milan Broz wrote: > > On 26/06/2019 09:15, Ard Biesheuvel wrote: > > > Thanks for the insight. So I guess we have consensus that MORUS should > > be removed. How about aegis128l and aegis256, which have been > > disregarded in favor of aegis128 by CAESAR (note tha

Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-26 Thread Milan Broz
On 26/06/2019 09:15, Ard Biesheuvel wrote: > Thanks for the insight. So I guess we have consensus that MORUS should > be removed. How about aegis128l and aegis256, which have been > disregarded in favor of aegis128 by CAESAR (note that I sent an > accelerated ARM/arm64 version of aegis128 based on

Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-26 Thread Ard Biesheuvel
On Wed, 26 Jun 2019 at 09:00, Milan Broz wrote: > > On 25/06/2019 20:37, Ard Biesheuvel wrote: > > On Tue, 25 Jun 2019 at 19:12, Eric Biggers wrote: > >> > >> [+Cc Milan] > > I was discussing this with Ondra before he sent the reply, anyway comments > below: > > >> On Tue, Jun 25, 2019 at 04:52:

Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-26 Thread Milan Broz
On 25/06/2019 20:37, Ard Biesheuvel wrote: > On Tue, 25 Jun 2019 at 19:12, Eric Biggers wrote: >> >> [+Cc Milan] I was discussing this with Ondra before he sent the reply, anyway comments below: >> On Tue, Jun 25, 2019 at 04:52:54PM +0200, Ard Biesheuvel wrote: >>> MORUS was not selected as a w

Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-25 Thread Ard Biesheuvel
On Tue, 25 Jun 2019 at 19:12, Eric Biggers wrote: > > [+Cc Milan] > > On Tue, Jun 25, 2019 at 04:52:54PM +0200, Ard Biesheuvel wrote: > > MORUS was not selected as a winner in the CAESAR competition, which > > is not surprising since it is considered to be cryptographically > > broken. (Note that

Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-25 Thread Geert Uytterhoeven
Hi Ard, On Tue, Jun 25, 2019 at 5:58 PM Ard Biesheuvel wrote: > On Tue, 25 Jun 2019 at 17:27, Geert Uytterhoeven wrote: > > On Tue, Jun 25, 2019 at 4:53 PM Ard Biesheuvel > > wrote: > > > MORUS was not selected as a winner in the CAESAR competition, which > > > is not surprising since it is con

Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-25 Thread Eric Biggers
[+Cc Milan] On Tue, Jun 25, 2019 at 04:52:54PM +0200, Ard Biesheuvel wrote: > MORUS was not selected as a winner in the CAESAR competition, which > is not surprising since it is considered to be cryptographically > broken. (Note that this is not an implementation defect, but a flaw > in the underl

Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-25 Thread Ard Biesheuvel
On Tue, 25 Jun 2019 at 17:27, Geert Uytterhoeven wrote: > > Hi Ard, > > On Tue, Jun 25, 2019 at 4:53 PM Ard Biesheuvel > wrote: > > MORUS was not selected as a winner in the CAESAR competition, which > > is not surprising since it is considered to be cryptographically > > broken. (Note that this

Re: [PATCH] crypto: morus - remove generic and x86 implementations

2019-06-25 Thread Geert Uytterhoeven
Hi Ard, On Tue, Jun 25, 2019 at 4:53 PM Ard Biesheuvel wrote: > MORUS was not selected as a winner in the CAESAR competition, which > is not surprising since it is considered to be cryptographically > broken. (Note that this is not an implementation defect, but a flaw > in the underlying algorith