From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: ZFS Crypto key hand off to kernel
Date: Fri, 13 Jan 2012 15:17:59 +0100 [thread overview]
Message-ID: <4F103D17.4020903@gmail.com> (raw)
In-Reply-To: <4F0C2DDE.7070703@Oracle.COM>
On 10.01.2012 13:23, Darren J Moffat wrote:
> I've been testing the ZFS Crypto support in GRUB2 with Solaris 11 and
> found it works great - many thanks!
>
> The 'zfskey' command works very nicely, however the key is only
> available to grub and isn't handed off to the kernel that GRUB2 starts
> up.
>
> I'm considering an extension to the multiboot2 spec to provide a
> mechanism to hand off the key from GRUB2 to the running kernel.
>
> I would like for this not to be specific to the ZFS crypto support but
> to be usable for LUKS and other systems that allow for an encrypted
> root/boot where both GRUB2 and the kernel need the same key.
>
> Is this something that would be of interest for GRUB2 ? If so I'll
> look at developing the spec update and a patch for GRUB2 to support it
> for the zfs crypto support.
>
That would be most welcome. The main issues are:
1) What to consider a key? IMHO it should be the master key, and not
password or session key.
2) How to match keys to actual devices? I think it should be UUID for
LUKS and POOLUUID+FSNAME for ZFS, or perhaps just POOLUUD.
3) GRUB may have some keys without knowing which pool/fs it's used for.
They should be marked as such.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2012-01-13 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 12:23 ZFS Crypto key hand off to kernel Darren J Moffat
2012-01-13 14:17 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-01-13 14:27 ` Darren J Moffat
2012-01-13 16:10 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4F103D17.4020903@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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.