All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Geoffrey Thomas <gthomas@mokafive.com>
Cc: "wad@chromium.org" <wad@chromium.org>,
	"dm-crypt@saout.de" <dm-crypt@saout.de>,
	"msb@chromium.org" <msb@chromium.org>,
	"ellyjones@chromium.org" <ellyjones@chromium.org>,
	Mikulas Patocka <mpatocka@redhat.com>,
	"agk@redhat.com" <agk@redhat.com>
Subject: Re: [dm-crypt] verity for GRUB?
Date: Wed, 10 Oct 2012 23:55:06 +0200	[thread overview]
Message-ID: <5075EEBA.6090609@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1210101434220.27430@salmon-of-wisdom>

On 10/10/2012 11:43 PM, Geoffrey Thomas wrote:
> On Wed, 10 Oct 2012, Milan Broz wrote:
> 
>> Is there anything from libcryptsetup you want to use or it is just about
>> kernel code?
>>
>> If you want to use code from cryptsetup (cryptsetup/lib/verity/*), what exactly
>> you need and which licence is ok for you (GPL2+ or LGPL?)
>> (GPL3 will be incompatible with other cryptsetup code.)
> 
> Hm. I _thought_ I could adapt lib/verity/verity_hash.c for what I need, 
> but it appears to only support a whole-disk verification, not verification 
> of individual blocks.

Well, yes, because cryptsetup does not need that.

Also it uses crypto backend wrappers, so I am afraid you cannot just take
this library without a lot of changes....

> That said, if you're willing to take patches to 
> extend libverity's API, I can add the functionality I need. I believe that 
> GPLv2+ should work fine for GRUB.

I see no major problem with relicensing (but need to check properly).
If it helps to use it more broadly, it would be nice (with available
source code for everyone).

If you have any patches, just send them (to list or create new issue
on project page).

What is not clear here (not related to problems above) is where
you want to store root hash and how grub2 will securely obtain it...

Thanks,
Milan

  reply	other threads:[~2012-10-10 21:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09  4:36 [dm-crypt] verity for GRUB? Geoffrey Thomas
2012-10-09  6:27 ` ffrizzy
2012-10-09  8:16   ` [dm-crypt] Unsubscribe requests Arno Wagner
2012-10-09  8:45     ` ffrizzy
2012-10-09  8:49       ` Ralf Ramsauer
2012-10-10 13:00 ` [dm-crypt] verity for GRUB? Mikulas Patocka
2012-10-10 20:51   ` Geoffrey Thomas
2012-10-10 21:20     ` Milan Broz
2012-10-10 21:23       ` Milan Broz
2012-10-10 21:43       ` Geoffrey Thomas
2012-10-10 21:55         ` Milan Broz [this message]
2012-10-10 22:04           ` Geoffrey Thomas
2012-10-11  5:10             ` Arno Wagner
2012-10-11  7:23               ` [dm-crypt] license of libcryptsetup (was: verity for GRUB?) Milan Broz
2012-10-11  9:21                 ` Arno Wagner

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=5075EEBA.6090609@redhat.com \
    --to=mbroz@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=ellyjones@chromium.org \
    --cc=gthomas@mokafive.com \
    --cc=mpatocka@redhat.com \
    --cc=msb@chromium.org \
    --cc=wad@chromium.org \
    /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.