From: "Michael Kjörling" <michael@kjorling.se>
To: dm-crypt@saout.de
Subject: [dm-crypt] Re: LUKS partition creation date
Date: Thu, 27 May 2021 11:03:52 +0000 [thread overview]
Message-ID: <1bfc79cc-3805-4594-a376-1b1959281890@localhost> (raw)
In-Reply-To: <20210527105438.GA5842@tansi.org>
On 27 May 2021 12:54 +0200, from arno@wagner.name (Arno Wagner):
>> Just a few more points (maybe we can later add this to FAQ):
>
> Good idea, will do.
Maybe the FAQ should even include a question that lists what _is_
stored in the LUKS header, with a note to the effect of "this is all
there is", and a link to the respective on-disk format specification.
I imagine that a summarized list that gives, for each of LUKS 1 and
LUKS 2, what is stored globally and per key slot, and for each whether
it's encrypted or unencrypted, would be quite informative.
Yes, that should all be in the detailed on-disk format specification,
but a summary would make the information much more accessible.
--
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
next prev parent reply other threads:[~2021-05-27 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 8:48 [dm-crypt] LUKS partition creation date Valdez
2021-05-27 5:56 ` [dm-crypt] " Michael Kjörling
2021-05-27 8:04 ` Milan Broz
2021-05-27 10:54 ` Arno Wagner
2021-05-27 11:03 ` Michael Kjörling [this message]
2021-05-27 12:05 ` Arno Wagner
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=1bfc79cc-3805-4594-a376-1b1959281890@localhost \
--to=michael@kjorling.se \
--cc=dm-crypt@saout.de \
/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;
as well as URLs for NNTP newsgroup(s).