From: Arno Wagner <firstname.lastname@example.org>
To: Lamy Geier <email@example.com>
Subject: Re: Single User (single or multiple keyslots with similar or different passphrase)
Date: Mon, 21 Nov 2022 14:26:30 +0100 [thread overview]
Message-ID: <20221121132630.GB22361@tansi.org> (raw)
One Keyslot should be enough, but you should hve a header backup.
The only redundancy multiple passphrases give you is basically
On Mon, Nov 21, 2022 at 09:42:37 CET, Lamy Geier wrote:
> 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
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: firstname.lastname@example.org
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:[~2022-11-21 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 8:42 Single User (single or multiple keyslots with similar or different passphrase) Lamy Geier
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 ` Arno Wagner [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).