DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: "shmick@riseup.net" <shmick@riseup.net>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] open ext-2/3/4 luks container, ext2fsd + FreeOTFE in Windows
Date: Tue, 26 Nov 2013 13:34:05 +0100	[thread overview]
Message-ID: <5294953D.5060807@gmail.com> (raw)
In-Reply-To: <52948EBF.6020604@riseup.net>

On 11/26/2013 01:06 PM, shmick@riseup.net wrote:
> does anybody have some working field notes they can pass on to get this
> working ?
> 
> when i attempt to open the luks container, FreeOTFE can't do it
> 
> in windows device manager the disk reports it must be initialised which
> will obviously destroy the luks header info

I think usual way is to create partition table with single partition
(and create LUKS on that partition)
IIRC device manager will not complain if there is a partition table.


> i may have better luck with a FAT/NTFS fs but i'd prefer to keep it
> native to linux and just use read only in Windows
> 
> my method was to simply first create the luks container, format it to
> ext4 and attempt to open in Windows with FreeOTFE

So you destroy LUKS header or keyslots by mkfs? This is wrong, don't do it.
It is just pure luck if it works. (It was actually kind of a bug in mkfs that it
did not destroy LUKS signature properly.)

Milan

      reply	other threads:[~2013-11-26 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22  8:26 [dm-crypt] re-format existing luks partition shmick
2013-11-22 10:33 ` Ondrej Kozina
2013-11-22 11:49   ` shmick
2013-11-22 14:19     ` Robert Nichols
2013-11-22 15:33       ` Arno Wagner
2013-11-26 12:06 ` [dm-crypt] open ext-2/3/4 luks container, ext2fsd + FreeOTFE in Windows shmick
2013-11-26 12:34   ` Milan Broz [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=5294953D.5060807@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=shmick@riseup.net \
    /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