From: Lamy Geier <lamyergeier@gmail.com>
To: cryptsetup@lists.linux.dev
Subject: Frequency of backup of headers for LUKS1 and LUKS2
Date: Mon, 21 Nov 2022 12:06:57 +0100 [thread overview]
Message-ID: <152dd874-c1ae-8190-9878-e69cada4edab@gmail.com> (raw)
In-Reply-To: <5b560ee4-2813-6aa5-484d-1754e118bb90@gmail.com>
Given that I won't add or remove any key from header key slot, or I
won't re-encrypt (i.e. change the master key), how often do I need to
backup the LUKS1 and LUKS2 header? Is doing the backup once enough and
making sure that the backup is not corrupted?
Are there any other situation where one needs to backup the headers of
LUKS1 and LUKS2 more often?
I was wondering if the contents of header changes in any other way, that
requires backup, if it affects restore possibility.
Thanks and Regards
Lamy
next prev parent reply other threads:[~2022-11-21 11:07 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 ` Lamy Geier [this message]
2022-11-21 13:24 ` Frequency of backup of headers for LUKS1 and LUKS2 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=152dd874-c1ae-8190-9878-e69cada4edab@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).