Bug#914136: marked as done (linux: enable CONFIG_CRYPTO_MORUS* and CONFIG_CRYPTO_AEGIS*)

2018-12-17 Thread Debian Bug Tracking System
Your message dated Mon, 17 Dec 2018 15:00:24 + with message-id and subject line Bug#914136: fixed in linux 4.19.9-1 has caused the Debian Bug report #914136, regarding linux: enable CONFIG_CRYPTO_MORUS* and CONFIG_CRYPTO_AEGIS* to be marked as done. This means that you claim that the problem

Re: linux: enable CONFIG_CRYPTO_MORUS* and CONFIG_CRYPTO_AEGIS*

2018-11-24 Thread Christoph Anton Mitterer
Hey. Just wondered if a maintainer could possibly tell me whether this could happen anytime soon? It's no big problem for me if not, I'd just want to avoid compiling the whole kernel on my system (which is not the fastest one ^^) if you'd enable it anyway on the next version or so. Cheers, Chri

Bug#914136: linux: enable CONFIG_CRYPTO_MORUS* and CONFIG_CRYPTO_AEGIS*

2018-11-19 Thread Christoph Anton Mitterer
Source: linux Version: 4.18.10-2+b1 Severity: wishlist Hi. Could you please enable the crypto modules for MORUS and AEGIS AEAD ciphers? It shoul be supported now in cryptsetup/dm-crypt for volumes with integrity protection and I'd like to play with them. Thanks, Chris. -- System Information: