From: Milan Broz <gmazyland@gmail.com>
To: Jan Janssen <medhefgo@web.de>, dm-crypt@saout.de
Subject: Re: [dm-crypt] Detached header
Date: Thu, 17 Apr 2014 20:27:43 +0200 [thread overview]
Message-ID: <53501D1F.4040904@gmail.com> (raw)
In-Reply-To: <53501984.9050004@web.de>
On 04/17/2014 08:12 PM, Jan Janssen wrote:
> Hi,
>
> I'm experimenting with LUKS detached header and I had the problem that
> cryptsetup binary does not like regular files when provided with
> --header (both luksFormat and open). When I make a manual losetup with
> the same header file and provide the loop device to --header everything
> works fine.
>
> According to the man page, --header is supposed to work for regular
> files too. This should either get fixed or the manual page be updated.
Detached header should works with regular files.
Can you provide more info what is not working? Please post failing command with
added --debug and provide exact versions of cryptsetup.
Milan
next prev parent reply other threads:[~2014-04-17 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 18:12 [dm-crypt] Detached header Jan Janssen
2014-04-17 18:21 ` Arno Wagner
2014-04-17 18:27 ` Milan Broz [this message]
2014-04-17 18:52 ` Jan Janssen
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=53501D1F.4040904@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=medhefgo@web.de \
/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