From: Milan Broz <gmazyland@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: pavankumar.p@globaledgesoft.com, Marian Csontos <mcsontos@redhat.com>
Subject: Re: DM-Verity Tool
Date: Wed, 22 May 2013 18:46:36 +0200 [thread overview]
Message-ID: <519CF66C.8010808@gmail.com> (raw)
In-Reply-To: <519CA6F0.3000309@redhat.com>
On 05/22/2013 01:07 PM, Marian Csontos wrote:
> On 05/21/2013 05:11 PM, pavankumar.p@globaledgesoft.com wrote:
>> Hello Mandeep,
>>
>> I was trying to download the source code to generate the hash from the
>> following location. But looks like this is moved. Pls share the latest git
>> hub location of the source.
>> http://git.chromium.org/cgi-bin/gitweb.cgi?p=dm-verity.git;a=tree
>
> Hi Pavan, dm-verity is in upstream kernel tree now:
>
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/md/dm-verity.c
I think the question was about tool to generate hash,
not the target itself.
In any case, dm-verity is in kernel and veritysetup tool is part of upstream
cryptsetup package.
Documentation to kernel dm-verity
http://code.google.com/p/cryptsetup/wiki/DMVerity
And some release notes info about veritysetup (see man page as well)
http://code.google.com/p/cryptsetup/wiki/Cryptsetup150
Milan
next prev parent reply other threads:[~2013-05-22 16:46 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 [this message]
2013-05-23 6:41 ` pavankumar.p
2013-05-23 20:47 ` Milan Broz
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=519CF66C.8010808@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-devel@redhat.com \
--cc=mcsontos@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.