All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Sun_Blood <sblood@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Protection against data failure
Date: Wed, 10 Aug 2011 10:43:34 +0200	[thread overview]
Message-ID: <4E4244B6.9020509@redhat.com> (raw)
In-Reply-To: <CAMN6oRmCT-s2XmeWTQ4PU1=OEPe40okeiZJ7cgnWwzz44ZpA7Q@mail.gmail.com>

On 08/10/2011 10:14 AM, Sun_Blood wrote:

> Lucky I see that cryptsesetup has the luksHeaderBackup function. (LVM
> also have a similar function).
> My question here is if I accidental overwrite the first 5% of the disk
> could I with this option restore and access the 95% rest of the system
> data?

Just short answer: both (luksHeaderBackup for LUKS and vgcfgbackup for LVM)
create backup of _metadata_ not the data.

With these backups you are able to recover LVM over LUKS mappings.
Take is as backup of /etc with configuration of your system - it is good
idea to regularly backup system config.

But it says nothing about data on volumes itself. So it is obviously not replacement
for normal data backup, just prerequisite.

> And I final question. The output from luksHeaderBackup how sensitive
> is that information? Is it like handing somebody my password if I
> store it on a local unencrypted disk?

It is written in man page. To decrypt drive you need LUKS header (or backup
of it - even old with old keyslots) AND passhprase to some keyslot in it.

LUKS header backup is basically just image of start of the disk - you
can create similar backup using dd.

See http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Backup_and_Data_Recovery

Milan

  reply	other threads:[~2011-08-10  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10  8:14 [dm-crypt] Protection against data failure Sun_Blood
2011-08-10  8:43 ` Milan Broz [this message]
2011-08-10 12:12 ` Marc Ballarin
2011-08-10 12:44   ` Sun_Blood
2011-08-13 11:51     ` Marc Ballarin
2011-08-10 17:26 ` 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=4E4244B6.9020509@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=sblood@gmail.com \
    /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.