From: Milan Broz <gmazyland@gmail.com>
To: Alex Lieflander <public@atlief.com>, cryptsetup@lists.linux.dev
Subject: Re: Authenticated Encryption with external Data Integrity Fields
Date: Tue, 2 Apr 2024 12:52:26 +0200 [thread overview]
Message-ID: <cc8e19fe-339d-418c-ac9a-846d22a369bb@gmail.com> (raw)
In-Reply-To: <22FA1250-CE63-4289-90F3-D2256762E5D0@atlief.com>
Hi,
On 4/2/24 4:15 AM, Alex Lieflander wrote:
> Hello,
>
> I’m trying to add authenticated encryption to my setup, but I’m
> having trouble to configure some of the parameters. I know that
> `cryptsetup` with --integrity only supports some of the options that
> `integritysetup` does, so I’m wondering if I could instead create the
> integrity layer myself and tell `cryptsetup` to pass down its
> integrity tags (like it does with the --integrity option).
No, you cannot do that. Authenticated encryption through dm-crypt
(with dm-integrity proividend only additional per-sector space) can
be configured only with LUKS2 and cryptsetup.
But the AEAD algorithm configuration for LUKS2 will need some update.
What is missing for your config?
> If that isn’t currently possible, are there any plans to add that
> feature in the future?
No, this is not planned. But see below.
> It could also be used to take advantage of physical hardware with T10/DIF support.
Existing hw formats usually only supports 512 + 8 bytes sector, this is not enough for AEAD.
But NVMe drives can be configured to actually support other per-sector additional space.
IMO this feature is currently available only to "enterprise" storage I do not have access to.
But once such configuration is reliable and available on some generic NVMe drives, I definitely
want to add support for it (IOW replace dm-integrity by this hw-only solution - this was actually
long-term plan; dm-integrity was originally only proof-of-concept.)
> Alternatively, are there any
> future plans to support using a separate device for the integrity
> tags like `integritysetup` can with --data-device?
No. We already support detached LUKS2 header, with separate device for integrity
tags this means maintaining 3 separate devices, this would create too complex scenario.
The long-term plan should head to hw backed support mentioned above, that would also
increase performance as it removes the need for dm-integrity journal.
Milan
next prev parent reply other threads:[~2024-04-02 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 2:15 Authenticated Encryption with external Data Integrity Fields Alex Lieflander
2024-04-02 10:52 ` Milan Broz [this message]
2024-04-02 23:20 ` Alex Lieflander
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=cc8e19fe-339d-418c-ac9a-846d22a369bb@gmail.com \
--to=gmazyland@gmail.com \
--cc=cryptsetup@lists.linux.dev \
--cc=public@atlief.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