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 17:25:59 +0200 [thread overview]
Message-ID: <4DFE1507.6020909@gmail.com> (raw)
In-Reply-To: <4DFE0D59.1090000@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
Thank you for your quick and clear answer Milan! Tha'ts really great! :D
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?
Best regards,
Patrick
Le 19. 06. 11 16:53, Milan Broz a écrit :
> On 06/19/2011 03:54 PM, Patrick wrote:
>> The case : I want to encrypt a full USB disk and my question is : is
>> it mandatory to have a partition existing on the device and to
>> luskformat the partition? In other words, is it OK to luksformat the
>> full device, without mentionning any partition? Is it off
>> "standards"?
> You can use whole device without partition table, there is no problem
> in Linux. For LUKS it is just block device - it is not important
> if it is partition or the whole device.
>
> There is only one situation, I know about, when using partition is safer.
>
> If you have portable disk (or USB flashdrive or whatever) and there
> is no partition table on it, and you plug such drive to
> another system (namely older version of Windows) it
> likes to offer you to "initialize" drive - which can destruct
> LUKS header there. If there is a partition table, it thinks that
> drive was already initialized preventing it.
> (I think it is not problem in recent versions but not sure.)
>
> Milan
[-- Attachment #2: Type: text/html, Size: 2011 bytes --]
next prev parent reply other threads:[~2011-06-19 15:26 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 [this message]
2011-06-19 15:46 ` Milan Broz
2011-06-19 17:47 ` Patrick
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=4DFE1507.6020909@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