From: Milan Broz <gmazyland@gmail.com>
To: pavankumar.p@globaledgesoft.com
Cc: Marian Csontos <mcsontos@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
mpatocka@redhat.com
Subject: Re: DM-Verity Tool
Date: Thu, 23 May 2013 22:47:40 +0200 [thread overview]
Message-ID: <519E806C.1050903@gmail.com> (raw)
In-Reply-To: <20204.192.168.200.1.1369291275.squirrel@gesmail.globaledgesoft.com>
On 05/23/2013 08:41 AM, pavankumar.p@globaledgesoft.com wrote:
> 1. What are the difference between configuring a verity target using
> dmsetup & veritysetup. Can these be used interchangeably?
dmsetup is just low level tool, you need to know all table parameters
while veritysetup will prepare table for you using high level commands
and on-disk metadata (if present).
> 2. I tried passing the root hash value generated by veritysetup as a
> parameter to dmsetup but this doesn't work. On doing dmsetup status, the
> output is showing as the target corrupted (C). I examined dmesg & found
> the following error
Be sure you are using proper parameters, metadata version etc.
Try activate device with veritysetup, then run "dmsetup table" and
check what is different in your dmsetup line.
> 3. After creating a verity target using "veritysetup" how to test the
> target for corrupted case (As soon as creating the status is Verified (V))
By corrupting the image? :) See tests/verity-compat-test in cryptsetup
tree, it is basic regression test which is simulating both data and hash
corruption (it just dd random data to know offset and expects failure.)
Milan
next prev parent reply other threads:[~2013-05-23 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 15:11 DM-Verity Tool pavankumar.p
2013-05-22 11:07 ` Marian Csontos
2013-05-22 16:00 ` pavankumar.p
2013-05-22 16:46 ` Milan Broz
2013-05-23 6:41 ` pavankumar.p
2013-05-23 20:47 ` Milan Broz [this message]
2013-05-24 16:10 ` pavankumar.p
2013-05-27 15:52 ` pavankumar.p
2013-05-30 16:28 ` pavankumar.p
2013-05-31 12:31 ` Mikulas Patocka
2013-05-31 16:15 ` pavankumar.p
2013-06-03 12:39 ` Will Drewry
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=519E806C.1050903@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-devel@redhat.com \
--cc=mcsontos@redhat.com \
--cc=mpatocka@redhat.com \
--cc=pavankumar.p@globaledgesoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.