archive mirror
 help / color / mirror / Atom feed
From: Arno Wagner <>
To: Lamy Geier <>
Subject: Re: Frequency of backup of headers for LUKS1 and LUKS2
Date: Mon, 21 Nov 2022 14:24:38 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Header backup is only needed if you change the header.
Data-area backup is another question.


On Mon, Nov 21, 2022 at 12:06:57 CET, Lamy Geier wrote:
> 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

Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email:
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

  reply	other threads:[~2022-11-21 13:31 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 [this message]
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:

* 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).