From: Milan Broz <gmazyland@gmail.com>
To: Patrick Callaghan <patrickc25000@hotmail.com>,
"cryptsetup@lists.linux.dev" <cryptsetup@lists.linux.dev>
Subject: Re: LUKS and quantum computing
Date: Tue, 26 Nov 2024 09:53:36 +0100 [thread overview]
Message-ID: <94a6a2f6-dc55-44ad-9172-6ac76e83abe3@gmail.com> (raw)
In-Reply-To: <PH7P220MB1325C03018B9E4F926B5127CED2E2@PH7P220MB1325.NAMP220.PROD.OUTLOOK.COM>
On 11/25/24 11:13 PM, Patrick Callaghan wrote:
> If we use LUKS encryption with SHA-256 configured (i.e. the
> default), is this considered safe against attacks by quantum
> computers?
SHA256 has no problem, specifically if used for PBKDF2
(iterative hashing for key derivation).
Default LUKS2 configuration no longer use SHA256 anyway, only for
antiforensic filter (split key material among more sectors) and
this is not a cryptographically relevant operation.
We use Argon2 with Blake2 hash internally for PBKDF now in LUKS2.
> I ask because NIST suggests SHA512 in general for quantum safe
> algorithms (see "old Q17" in https://csrc.nist.gov/projects/post-
> quantum-cryptography/faqs) and we want to be LUKS quantum safe now
> and for several years to come, even if no practical attacks
> currently exist.
>
> Note, the cipher we use is "aes-xts-plain64" so we have no question
> about this as AES with 256-bit keys is considered quantum safe.
The 256bit (2x256 bit for XTS) key is default, this is according to
what is suggested in general (even in the context of QC).
Otherwise there should be no problem with symmetric encryption related
to quantum computing.
BTW who is "we" in your pararaph?
Milan
next prev parent reply other threads:[~2024-11-26 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 22:13 LUKS and quantum computing Patrick Callaghan
2024-11-26 8:39 ` Arno Wagner
2024-11-26 8:53 ` Milan Broz [this message]
2024-11-26 9:34 ` Arno Wagner
2024-11-26 21:49 ` Patrick Callaghan
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=94a6a2f6-dc55-44ad-9172-6ac76e83abe3@gmail.com \
--to=gmazyland@gmail.com \
--cc=cryptsetup@lists.linux.dev \
--cc=patrickc25000@hotmail.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