From: Patrick <mailorp@gmail.com>
To: Milan Broz <mbroz@redhat.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Partition mandatory?
Date: Sun, 19 Jun 2011 19:47:45 +0200 [thread overview]
Message-ID: <4DFE3641.7070100@gmail.com> (raw)
In-Reply-To: <4DFE19CB.1010701@redhat.com>
Yes, sure I'll do!
Thanks again for your answers!
Best regards,
Patrick
Le 19. 06. 11 17:46, Milan Broz a écrit :
> On 06/19/2011 05:25 PM, Patrick wrote:
>> So, in the case of such a header destruction by an "old" OS, I think
>> it is still possible to restore the header I saved using
>>
>> _luksHeaderBackup_ <device> --header-backup-file <file>
>>
>> doing
>>
>> _luksHeaderRestore_ <device> --header-backup-file <file>
>>
>> Correct?
> yes, but it s just backup of LUKS header. Not a backup of data inside:-)
> (with old header backup and passphrase you can unlock the drive,
> so store it on safe place)
>
> Milan
>
>
prev parent reply other threads:[~2011-06-19 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 13:54 [dm-crypt] Partition mandatory? Patrick
2011-06-19 14:53 ` Milan Broz
2011-06-19 15:25 ` Patrick
2011-06-19 15:46 ` Milan Broz
2011-06-19 17:47 ` Patrick [this message]
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=4DFE3641.7070100@gmail.com \
--to=mailorp@gmail.com \
--cc=dm-crypt@saout.de \
--cc=mbroz@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox