From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: [dm-crypt] FAQ rework for LUKS2: First pass done
Date: Sun, 26 Apr 2020 18:31:51 +0200 [thread overview]
Message-ID: <20200426163151.GA2466@tansi.org> (raw)
Hi all,
I just finished the firsy pass through the FAQ to adapt it for LUKS2.
In particular I did the following:
- Clearly state LUKS1 or LUKS2 for things that do not apply to both
- Still uses "LUKS" when both LUKS1 or LUKS2 are affected
- Added references for LUKS2 header spec
- Added specific instructions for LUKS2 where needed
- Added a (currently pretty short) LUKS2 section
If some of you find the time to read through it and let me know
about any errors or omissions, I would apprecitate it.
Also, if you have any suggestions for Section 10 (LUKS2 Questions),
or mabybe even a small item to add, I would appreciate that as
well. In particular, the LUKS2 section would benefit from some
mini-HOWTOs, I think.
As usual, the FAQ is found at
https://gitlab.com/cryptsetup/cryptsetup/-/wikis/FrequentlyAskedQuestions
I did update the version in the sources as well, but that may take a while
to propagate.
Regards,
Arno
--
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 reply other threads:[~2020-04-26 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 16:31 Arno Wagner [this message]
[not found] <111354031.932645.1587998242849.ref@mail.yahoo.com>
2020-04-27 14:37 ` [dm-crypt] FAQ rework for LUKS2: First pass done JT Morée
2020-04-28 13:30 ` 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=20200426163151.GA2466@tansi.org \
--to=arno@wagner.name \
--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 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.