[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190209215219.GA688@sol.localdomain>
Date: Sat, 9 Feb 2019 13:52:20 -0800
From: Eric Biggers <ebiggers@...nel.org>
To: Iuliana Prodan <iuliana.prodan@....com>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
Horia Geanta <horia.geanta@....com>,
Aymen Sghaier <aymen.sghaier@....com>,
"David S. Miller" <davem@...emloft.net>,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-imx <linux-imx@....com>
Subject: Re: [PATCH 0/4] crypto: caam - add ecb mode support
Hi Iuliana,
On Fri, Feb 08, 2019 at 03:50:06PM +0200, Iuliana Prodan wrote:
> This patch set adds ecb mode support for aes, des, 3des and arc4 ciphers.
> skcipher implementation is reused, making sure to handle the no IV case.
>
> While here:
> -fix a DMA API issue where initial src/dst_nents are used instead of nents
> returned by dma_map_sg()
> -export arc4 defines in a common header
> -update cbc des and 3des to check for weak keys
>
> Iuliana Prodan (4):
> crypto: caam - use mapped_{src,dst}_nents for job descriptor
> crypto: export arc4 defines
> crypto: caam - add ecb(*) support
> crypto: caam - weak key checking for cbc des, 3des
>
Do you have an actual use case for adding more DES, 3DES, and ARC4
implementations, or are you simply adding them because the hardware happens to
supports it? These old ciphers are insecure, so IMO more implementations should
only be added if there is a real use case where they're absolutely needed.
- Eric
Powered by blists - more mailing lists