From: Arno Wagner <wagner@arnowagner.info>
To: Patrick Callaghan <patrickc25000@hotmail.com>
Cc: "cryptsetup@lists.linux.dev" <cryptsetup@lists.linux.dev>
Subject: Re: LUKS and quantum computing
Date: Tue, 26 Nov 2024 09:39:01 +0100 [thread overview]
Message-ID: <Z0WJJaVuLpcIbkDG@tansi.org> (raw)
In-Reply-To: <PH7P220MB1325C03018B9E4F926B5127CED2E2@PH7P220MB1325.NAMP220.PROD.OUTLOOK.COM>
No idea. And frankly, I have stopped caring. "Quantum Computing" is
a Fata Morgana that does not amount to anything practical at this
time (after 50 years of resarch) and may well never amount to anything.
It will certainly not be a real treat in the foreseeable future.
Here is what Peter Gitman thinks of the topic, and I think it
is spot on: https://www.cs.auckland.ac.nz/~pgut001/pubs/bollocks.pdf
Regards,
Arno
On Mon, Nov 25, 2024 at 23:13:17 CET, 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?
>
> 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.
>
> Thank you.
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2024-11-26 8:45 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 [this message]
2024-11-26 8:53 ` Milan Broz
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=Z0WJJaVuLpcIbkDG@tansi.org \
--to=wagner@arnowagner.info \
--cc=arno@wagner.name \
--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