From: Lamy Geier <lamyergeier@gmail.com>
To: cryptsetup@lists.linux.dev
Subject: Single User (single or multiple keyslots with similar or different passphrase)
Date: Mon, 21 Nov 2022 09:42:37 +0100 [thread overview]
Message-ID: <5b560ee4-2813-6aa5-484d-1754e118bb90@gmail.com> (raw)
Hello!
I am a single user and owner of the data in my laptop. I was wondering
if it is any better to have single or multiple keyslots with same or
different passphrases. I am using LUKS2 on a partition for root, home
and swap volumes (LVM). And LUKS1 for a boot partition. Please suggest
which of the following is better choice and why:
1. Should I have single passphrase and single keyslot for LUKS1 and LUKS2?
2. Multiple Keyslots for LUKS1 and LUKS2 with same passphrase.
3. Multiple Keyslots for LUKS1 and LUKS2 with different passphrase.
- My reasoning was that may be having redundant information, it helps in
times of crisis for recovery.
- Note: The data will be owned and used only by me.
--
Thanks and Regards
Lamy
next reply other threads:[~2022-11-21 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 8:42 Lamy Geier [this message]
2022-11-21 11:06 ` Frequency of backup of headers for LUKS1 and LUKS2 Lamy Geier
2022-11-21 13:24 ` Arno Wagner
2022-11-21 13:26 ` Single User (single or multiple keyslots with similar or different passphrase) 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=5b560ee4-2813-6aa5-484d-1754e118bb90@gmail.com \
--to=lamyergeier@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).