Date: Wed, 15 Nov 2017 21:29:44 -0500 From: Eric McCorkle <eric@metricspace.net> To: Tommi Pernila <tommi.pernila@iki.fi>, Warner Losh <imp@bsdimp.com> Cc: "[ScaleEngine] Allan Jude" <allan.jude@scaleengine.com>, freebsd-current <freebsd-current@freebsd.org>, "imp@freebsd.org" <imp@freebsd.org> Subject: Re: GELI with UEFI supporting Boot Environments goes to HEAD when? Message-ID: <0e75a2ba-9a59-8301-a678-68a822025bd6@metricspace.net> In-Reply-To: <CABHD1wQU_6wHw96%2BLguVuqmwqY04%2Bn7NPcy6rSgn4QdKZpF3Kg@mail.gmail.com> References: <CABHD1wRyrmXp5R_ViERa-MnJnVKN-U551SWt%2Behm6r%2B3viydxg@mail.gmail.com> <CANCZdfp-bYi2fFJi5ashPLwjnwKWeoepiPt23LfPORU1EpKNGg@mail.gmail.com> <CABHD1wQU_6wHw96%2BLguVuqmwqY04%2Bn7NPcy6rSgn4QdKZpF3Kg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --TuJl2cvUGugu9FKn7FNqgU3PR8SRBD3wm Content-Type: multipart/mixed; boundary="aSdmjuiWiegWiQkoIfkT5ugO08cMQUc7w"; protected-headers="v1" From: Eric McCorkle <eric@metricspace.net> To: Tommi Pernila <tommi.pernila@iki.fi>, Warner Losh <imp@bsdimp.com> Cc: "[ScaleEngine] Allan Jude" <allan.jude@scaleengine.com>, freebsd-current <freebsd-current@freebsd.org>, "imp@freebsd.org" <imp@freebsd.org> Message-ID: <0e75a2ba-9a59-8301-a678-68a822025bd6@metricspace.net> Subject: Re: GELI with UEFI supporting Boot Environments goes to HEAD when? References: <CABHD1wRyrmXp5R_ViERa-MnJnVKN-U551SWt+ehm6r+3viydxg@mail.gmail.com> <CANCZdfp-bYi2fFJi5ashPLwjnwKWeoepiPt23LfPORU1EpKNGg@mail.gmail.com> <CABHD1wQU_6wHw96+LguVuqmwqY04+n7NPcy6rSgn4QdKZpF3Kg@mail.gmail.com> In-Reply-To: <CABHD1wQU_6wHw96+LguVuqmwqY04+n7NPcy6rSgn4QdKZpF3Kg@mail.gmail.com> --aSdmjuiWiegWiQkoIfkT5ugO08cMQUc7w Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Right, so basically, the remaining GELI patches are against loader, and most of them can go in independently of the work on removing boot1. There's a unanimous consensus on getting rid of boot1 which includes its original author, so that's going to happen. For GELI, we have the following (not necessarily in order): a) Adding the KMS interfaces, pseudo-device, and kernel keybuf interactio= ns b) Modifications to the efipart driver c) boot crypto d) GELI partition types (not strictly necessary) Then there's the GELI driver itself. (a) and (c) are good to land, (b) needs some more work after Toomas Soome pointed out a legitimate problem, and (d) actually needs a good bit more code (but again, it's more cosmetic). Additionally, the GELI driver will need further mods to efipart to be written (nothing too big). But we could go ahead with (a) and (c), as they've already been proven to work. I'd wanted to have this stuff shaped up sooner, but I'm preoccupied with the 7th RISC-V workshop at the end of the month. Once this stuff is all in, loader should handle any GELI volumes it finds, and it should Just Work once boot1 is gone. --aSdmjuiWiegWiQkoIfkT5ugO08cMQUc7w-- --TuJl2cvUGugu9FKn7FNqgU3PR8SRBD3wm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iIsEARYIADMWIQTp6hWnRH4nHb9/QN/kI/o6qzq6mAUCWgz4HBUcZXJpY0BtZXRy aWNzcGFjZS5uZXQACgkQ5CP6Oqs6uph1VwEA0/1XCpe5ATbW1m3TKtFPEjRHPvTz dPCXkADdIZ6CJuYA/1jucALr9LRVSUsSe+gy288Tv7T2E35GDFFOOeqKlxkE =P/s0 -----END PGP SIGNATURE----- --TuJl2cvUGugu9FKn7FNqgU3PR8SRBD3wm--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0e75a2ba-9a59-8301-a678-68a822025bd6>