From: Arno Wagner <wagner@arnowagner.info>
To: Alexander Grund <alexander.grund@tu-dresden.de>
Cc: cryptsetup@lists.linux.dev
Subject: Re: Are there known security issues during creation of LUKS containers?
Date: Sat, 17 May 2025 12:30:43 +0200 [thread overview]
Message-ID: <aChlU6dvZRH8AjIf@tansi.org> (raw)
In-Reply-To: <8a487ad4-b0a7-46ec-9969-d16da7607998@tu-dresden.de>
Hi Alexander,
there should not be any issues. AFAIK, everything critical is done in
locked memory and the only things going to disk are the ones that stay
there.
Obviously, if you have, say, a keylogger active when entering a
passphrase, that is an issue. But that is not different from
what happens with an exiting container.
As to documentation, that would be the LUKS specification.
Regards,
Arno
On Fri, May 16, 2025 at 14:29:00 CEST, Alexander Grund wrote:
> Hi all,
>
> we are planning to use LUKS containers on machines with limited local
> storage but access to a large, but shared file system.
> So far I've only found security considerations for existing LUKS containers.
>
> Are there any information on issues possible during **creation** of a LUKS
> container?
> I.e. if it is possible for someone with access to files on the file system,
> where the container is being created by `cryptsetup luksFormat`, is able to
> infer any information on the key during the process?
>
> Can anyone point me to relevant information/research?
>
> Thanks,
> Alexander Grund
>
--
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
prev parent reply other threads:[~2025-05-17 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d936a762-b75b-46b6-9fe7-1652c10afb6d@tu-dresden.de>
2025-05-16 12:29 ` Are there known security issues during creation of LUKS containers? Alexander Grund
2025-05-17 10:30 ` Arno Wagner [this message]
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=aChlU6dvZRH8AjIf@tansi.org \
--to=wagner@arnowagner.info \
--cc=alexander.grund@tu-dresden.de \
--cc=arno@wagner.name \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox