From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Integrating a FreeBSD/GELI change
Date: Sat, 1 Apr 2017 16:57:05 +0300 [thread overview]
Message-ID: <8da05611-54db-25c9-31c0-ca91a96252b6@gmail.com> (raw)
In-Reply-To: <5098c6fc-7ab5-6386-4ae2-a3fe2a343de4@metricspace.net>
[-- Attachment #1.1: Type: text/plain, Size: 2226 bytes --]
01.04.2017 15:57, Eric McCorkle пишет:
> Hello,
>
> I've been working on a series of changes designed to expand FreeBSD's
> full-disk encryption support via GELI (its preferred disk encryption
> mechanism). One of the important parts of this landed in HEAD last night:
>
> https://github.com/freebsd/freebsd/commit/6a205a32527153697eb4df4114ff0cd3c7cd6fd8
>
> This adds a general mechanism for passing keys into the FreeBSD kernel
> at boot. At present, this is used exclusively by the GELI subsystem.
>
> FreeBSD currently supports full-disk encryption for i386 BIOS. I am
> actively working on EFI support and would like to make sure that GRUB
> also supports full-disk encryption as well (as GRUB is our best option
> for a coreboot setup).
>
>
> Basically, to add support for this, I'd need to do two things:
>
> 1) Ensure that GRUB can handle an entirely GELI-encrypted disk hosting a
> FreeBSD system (I suspect it can, but I've never done a GRUB/GELI setup
> before)
>
> 2) An additional metadata item needs to get generated when booting the
> FreeBSD kernel that contains all the GELI keys. (For those who don't
> know, FreeBSD has a kernel metadata mechanism that is used to pass some
> information into the kernel: for example, the EFI console on EFI, some
> BIOS information on i386 BIOS, and so on)
>
>
> I've never submitted a patch to GRUB before, so I'm interested in 1) how
> hard would this be,
I suppose like with any other software project of reasonable size.
> 2) where should I look in the source code, and
GELI is in grub-core/disk/geli.c, generic framework for device
encryption (which GELI plugs in) in grub-core/disk/cryptodisk.c and
FreeBSD loader in grub-core/loader/i386/bsd*.
There was proposed patch that stored secret in environment variable that
was later used by loader (I think; I am not sure whether loader part was
actually implemented). Search this list for subject
Patch to support GELI passphrase passthrough
from Kris Moore (October 2014)
> 3) what is the procedure for submitting patches like this?
>
Just send patches to this list. Better inline using git send-email to
make it easier to comment.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-04-01 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 12:57 Integrating a FreeBSD/GELI change Eric McCorkle
2017-04-01 13:57 ` Andrei Borzenkov [this message]
2017-04-01 16:32 ` Eric McCorkle
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=8da05611-54db-25c9-31c0-ca91a96252b6@gmail.com \
--to=arvidjaar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).