From: Milan Broz <mbroz@redhat.com>
To: Wesley Miaw <wmiaw@netflix.com>
Cc: "dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] veritysetup support for files
Date: Fri, 10 Aug 2012 13:12:40 +0200 [thread overview]
Message-ID: <5024ECA8.9050509@redhat.com> (raw)
In-Reply-To: <FBC09D4B-6CF5-49AD-8BEA-20F04C920CFA@netflix.com>
On 08/09/2012 07:27 PM, Wesley Miaw wrote:
> The result I need is one file that contains a filesystem image (this
> would have already been created ahead of time), a second file that
> contains the raw hash data for that filesystem image, and a third
> file containing the dm-verity table parameters. I am creating the
> last file by redirecting veritysetup stdout to a file.
Ah, ok. So your only request is that raw hash data image is created
automatically as file (if parameter is not a block device directly)
and that this file doesn't need to be pre-allocated, correct?
I think I can do it even without introducing new library function
(I really do not want next context constructor type here).
I'll reply once I will have something ready for testing.
Milan
next prev parent reply other threads:[~2012-08-10 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 17:27 [dm-crypt] veritysetup support for files Wesley Miaw
2012-08-10 11:12 ` Milan Broz [this message]
2012-08-13 10:02 ` Milan Broz
2012-08-13 21:21 ` Wesley Miaw
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=5024ECA8.9050509@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=wmiaw@netflix.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