Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #67567 > unrolled thread

Bug#965330: linux-image-5.7.0-1-amd64: Please enable CONFIG_CRYPTO_ADIANTUM

Back to article view | Back to linux.debian.kernel

Contents

  Bug#965330: linux-image-5.7.0-1-amd64: Please enable CONFIG_CRYPTO_ADIANTUM schauveau <stephane@chauveau-central.net> - 2020-07-19 19:10 +0200
    Bug#965330: marked as done (linux-image-5.7.0-1-amd64: Please  enable CONFIG_CRYPTO_ADIANTUM) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-01-20 15:30 +0100

#67567 — Bug#965330: linux-image-5.7.0-1-amd64: Please enable CONFIG_CRYPTO_ADIANTUM

Package: src:linux
Version: 5.7.6-1
Severity: wishlist


Dear Maintainer,

I noticed that the Adiantum cipher is not enabled in the Debian kernels.

https://security.googleblog.com/2019/02/introducing-adiantum-encryption-for.html
To summarize, Adiantum is a cipher for disk encryption that was designed to b very efficient
on low-end devices lacking without hardware support for AES. A typical use case would
be a low-end android device or a single-board computer like the Raspberry Pi.

I am not necessarily talking about running the Debian kernel on those low-end
devices since they usually come with a custom kernel. The real problem is the
difficulty to mount those encrypted disks coming on my intel-based Debian
servers machines (for boot-strap, backup, recovery or any other maintenance reason).

[toc] | [next] | [standalone]

#69196 — Bug#965330: marked as done (linux-image-5.7.0-1-amd64: Please enable CONFIG_CRYPTO_ADIANTUM)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Wed, 20 Jan 2021 15:13:06 +0100
with message-id <20210120141306.w45yey4pohp46ry5@shell.thinkmo.de>
and subject line Re: Bug#965330: linux-image-5.7.0-1-amd64: Please enable CONFIG_CRYPTO_ADIANTUM
has caused the Debian Bug report #965330,
regarding linux-image-5.7.0-1-amd64: Please enable CONFIG_CRYPTO_ADIANTUM
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
965330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965330
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web