From: pavankumar.p@globaledgesoft.com
To: Milan Broz <gmazyland@gmail.com>,
mpatocka@redhat.com,
device-mapper development <dm-devel@redhat.com>,
Marian Csontos <mcsontos@redhat.com>
Subject: [Fwd: Re: DM-Verity Tool]
Date: Fri, 31 May 2013 18:58:08 +0530 (IST) [thread overview]
Message-ID: <62980.192.168.200.1.1370006888.squirrel@gesmail.globaledgesoft.com> (raw)
---------------------------- Original Message ----------------------------
Subject: Re: DM-Verity Tool
From: pavankumar.p@globaledgesoft.com
Date: Mon, May 27, 2013 9:22 pm
To: "Milan Broz" <gmazyland@gmail.com>
mpatocka@redhat.com
"device-mapper development" <dm-devel@redhat.com>
"Marian Csontos" <mcsontos@redhat.com>
--------------------------------------------------------------------------
Hello Mikulas,
> 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.)
In tests/verity-compat-test, in the following line
"check_root_hash 512
9de18652fe74edfb9b805aaed72ae2aa48f94333f1ba5c452ac33b1c39325174 $SALT 1
sha256 8388608"
How's the last parameter (hash_offset) calculated? it's hard coded
here(8388608).
Regards,
Pavan
> Hi All,
>
> Thanks a lot for your support. Now I am able to configure verity target
> using both veritysetup & dmsetup.
>
> Regards,
> Pavan
>
>
>>
>> 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 reply other threads:[~2013-05-31 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 13:28 pavankumar.p [this message]
2013-06-03 14:29 ` [Fwd: Re: DM-Verity Tool] Mikulas Patocka
2013-06-05 15:59 ` DM-Verity pavankumar.p
2013-06-06 14:41 ` DM-Verity 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=62980.192.168.200.1.1370006888.squirrel@gesmail.globaledgesoft.com \
--to=pavankumar.p@globaledgesoft.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=mcsontos@redhat.com \
--cc=mpatocka@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 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.