From: Alex Lieflander <atlief@icloud.com>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de, Christoph Anton Mitterer <calestyo@scientia.net>
Subject: [dm-crypt] Re: Is AES-GCM still a bad idea?
Date: Sun, 28 Nov 2021 15:35:14 -0500 [thread overview]
Message-ID: <6C23A020-AB65-4244-8492-059D63BCF8A6@icloud.com> (raw)
In-Reply-To: <9d41d409-cd44-743a-2020-ecbf20b20768@gmail.com>
Thanks for the prompt response!
> On Nov 28, 2021, at 9:58 AM, Milan Broz wrote:
>> On 11/28/21 06:50, Alex Lieflander wrote:
>> Hello,
>> My situation is quite similar to a thread posted a few months ago ("AEAD, recommended alogs and some more questions”), but it was pretty long and I don’t think it got any responses.
>> I’m hoping that a simplified version might be more approachable. Partial answers are welcome as well.
>> 1) Is aes-gcm-random still unsuitable for “normal” use?
>> 2) If so, are there any plans or estimates for when this might be improved/fixed?
>
> I think the best option for now is perhaps to use AEGIS ("--cipher aegis128-random --key-size 128 --integrity aead" in cryptsetup notation).
>
> Note that AEGIS256 was removed from recent kernels, see
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=520c1993bbe620e39fd93de1a01b9e0dc0b97aa6
>
> Also see https://github.com/jedisct1/draft-aegis-aead
I appreciate the suggestion, but I was really hoping for something that supported 192-bit AES encryption.
> But still, AEAD (authenticated encryption) in LUKS2 is experimental, so it depends what is the "normal" use for you.
>
> All this really depends what kernel crypto API provides, if we have some better option there, it is trivial to add to cryptsetup.
>
> Milan
Speaking of which, does cryptsetup support AES-GCM-SIV? I seem to be able to create devices with "--cipher aes-gcm-siv --integrity aead” but I can’t open them.
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
next prev parent reply other threads:[~2021-11-28 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 5:50 [dm-crypt] Is AES-GCM still a bad idea? Alex Lieflander
2021-11-28 14:58 ` [dm-crypt] " Milan Broz
2021-11-28 20:35 ` Alex Lieflander [this message]
2021-11-28 20:51 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6C23A020-AB65-4244-8492-059D63BCF8A6@icloud.com \
--to=atlief@icloud.com \
--cc=calestyo@scientia.net \
--cc=dm-crypt@saout.de \
--cc=gmazyland@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).