[dm-crypt] cryptsetup with kernel crypto backend and sha384

[dm-crypt] cryptsetup with kernel crypto backend and sha384

[Simon Weissberg]

Hi,

I noticed that the struct hash_algs in crypto_kernel.c does not contain an entry for the sha384 algorithm. (https://gitlab.com/cryptsetup/cryptsetup/blob/v2.0.6/lib/crypto_backend/crypto_kernel.c#L50)

This prevents sha384 from being used with the kernel crypto backend while it is usable with the gcrypt backend. Is there a particular reason for this?

Best regards,
Simon Fabian Weißberg
Software Developer

Rohde & Schwarz Cybersecurity GmbH
Lise-Meitner-Allee 4, D-44801 Bochum
www.cybersecurity.rohde-schwarz.com

Executive Board: Reik Hesselbarth; Company's Place of Business: Munich
Commercial Register No.: HRB 160333, VAT Identification No.: DE 295078969
WEEE Register Nr.: DE 138 891 79

Re: [dm-crypt] cryptsetup with kernel crypto backend and sha384

[Milan Broz]

On 27/12/2018 11:38, Simon Weissberg wrote:
> I noticed that the struct hash_algs in crypto_kernel.c does not
> contain an entry for the sha384 algorithm.
> (https://gitlab.com/cryptsetup/cryptsetup/blob/v2.0.6/lib/crypto_backend/crypto_kernel.c#L50)
>
>  This prevents sha384 from being used with the kernel crypto backend
> while it is usable with the gcrypt backend. Is there a particular
> reason for this?

It is just workaround for the crypto backend (there was not a reliable way to get some
information from kernel without crypto module already loaded), I will either add some more
dynamic option or add the sha384 to the list (despite I am not sure why you want to use it :).

Please could you just create a new issue for it to not forget about it?
https://gitlab.com/cryptsetup/cryptsetup/issues

Thanks,
Milan