Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 May 2016 10:27:40 -0400
From:      Allan Jude <allanjude@freebsd.org>
To:        freebsd-hackers@freebsd.org
Subject:   Re: EFI GELI support ready for testers
Message-ID:  <d6b96a6c-4e92-35a5-e78b-cc674b6d2f25@freebsd.org>
In-Reply-To: <20160528083656.GT38613@kib.kiev.ua>
References:  <519CC1FC-84DF-4710-8E62-AF26D8AED2CF@metricspace.net> <20160528083656.GT38613@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-05-28 04:36, Konstantin Belousov wrote:
> On Fri, May 27, 2016 at 07:39:57PM -0400, Eric McCorkle wrote:
>> I am pleased to announce that my work to add support for GELI in the EFI boot loader (as well as perform more general refactoring) is now ready for testing.  I am able to successfully detect multiple GELI partitions in boot1 and pass the keys into the kernel.
> 
> Can somebody explain in which way this is useful ?
> Same question for the GELI code for non-EFI loader.
> 
> BIOS cannot read raw data from the encrypted partition, so you need
> either old boot or the loader and some additional data on EFI boot
> partition anyway.
> 
> Features adds significant amount of code, which must be maintained in
> parallel with the kernel code.
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
> 

The motivation for my work (GELI in boot2 and loader for non-EFI boot)
was supporting ZFS boot environments. Previously, when you use GELI you
needed to have two ZFS pools, one for an unencrypted /boot and one for
the encrypted /

This breaks ZFS boot environments, since a snapshot of the root file
system won't include the correct kernel etc.

The final version of my geliboot took an extra effort to reuse the AES
code from sys/crypto/rijndael and sys/opencrypto and GELI directly from
sys/geom/eli to avoid maintaining a separate copy of that code in sys/boot

Hopefully the work I did to make sys/opencrypto and sys/geom/eli more
reusable outside of the kernel will make it easier for Eric to do the
same for the EFI version.

The motivation for the EFI version is the same, ZFS boot environments,
plus the obvious security advantages of having the kernel stored
encrypted rather than not.

-- 
Allan Jude



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d6b96a6c-4e92-35a5-e78b-cc674b6d2f25>