From: Milan Broz <gmazyland@gmail.com>
To: cryptsetup development <cryptsetup@lists.linux.dev>
Subject: New requirements for XTS encryption mode (IEEE 1619 standard)
Date: Thu, 27 Feb 2025 22:19:29 +0100 [thread overview]
Message-ID: <9ebe4e65-e5ee-4eb3-b0db-90de426c7863@gmail.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1178 bytes --]
Hi,
Many disk encryption systems currently utilize AES-XTS encryption, which is the default for LUKS and plain mode in cryptsetup.
A recent draft of the IEEE AES-XTS standard proposed new requirements for XTS implementation, notably the mandatory use of key scopes. Unfortunately, this draft is behind a paywall; even with a paid subscription, IEEE requires additional fees to download it.
These changes will significantly impact LUKS (and likely many other open-source software projects that utilize XTS mode). In light of this, we prepared an independent summarization paper explaining the issues associated with XTS mode.
Our paper is now available under a CC-BY license on Arxiv:
*XTS Mode Revisited: High Hopes for Key Scopes?*
https://arxiv.org/abs/2502.18631
I welcome any comments, additional information, or suggestions. The source of the paper is available on my GitHub: https://github.com/mbroz/xts-paper, where you can create issues to share your thoughts.
Thanks,
Milan
[1] P1619/D12, Oct 2024 - IEEE Draft Standard for Cryptographic Protection of Data on Block-Oriented Storage Devices
https://ieeexplore.ieee.org/document/10720727
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 4753 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-02-27 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 21:19 Milan Broz [this message]
2025-02-28 22:13 ` New requirements for XTS encryption mode (IEEE 1619 standard) Darek Hisc
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=9ebe4e65-e5ee-4eb3-b0db-90de426c7863@gmail.com \
--to=gmazyland@gmail.com \
--cc=cryptsetup@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.