I run Arch Linux as an encrypted /, /boot and swap system. That encrypted /boot
is nothing more than a folder under /, however two Keyslots are required to
boot.
If I understand the boot process correctly, LUKS Keyslot 1 is used by grub to
unlock /boot, then control is handed off to the kernel
t; On 8/28/20 11:28 AM, HardenedArray via Grub-devel wrote:
>
> > I run Arch Linux as an encrypted /, /boot and swap system. That
> > encrypted /boot is nothing more than a folder under /, however two
> > Keyslots are required to boot.
> > If I understand the boot process
st 28, 2020 4:51 PM, Patrick Steinhardt wrote:
> On Fri, Aug 28, 2020 at 11:37:24AM -0400, Eli Schwartz wrote:
>
> > On 8/28/20 11:28 AM, HardenedArray via Grub-devel wrote:
> >
> > > I run Arch Linux as an encrypted /, /boot and swap system. That
> > > encrypted
n my initial reply.
> > > - Forwarded message from Patrick Steinhardt p...@pks.im -
> > >
> > > > From: Patrick Steinhardt p...@pks.im
> > > > To: The development of GNU GRUB grub-devel@gnu.org
> > > > Date: Fri, 28 Aug 2020 18:51:21 +02
Hi Patrick,
As a direct consequence of your valuable `--modules=` input, I have taken the
time and attempted to carefully document my entire LUKS2 unlocking encrypted
/boot process for the benefit of others, similarly situated.
My procedure and comments are posted at:
https://aur.archlinux.or
19 PM, Patrick Steinhardt wrote:
> On Sun, Aug 30, 2020 at 03:30:39PM +0000, HardenedArray via Grub-devel wrote:
>
> > As a direct consequence of your valuable `--modules=` input, I have
> > taken the time and attempted to carefully document my entire LUKS2
> > unlocking
As a heads up to those working on the Secure Boot aspects of grub, I wanted to
provide the grub-2:2.06rc1-2 installation messages being shown to Arch Linux
grub users during a 'pacman -Syu' run that happens to pull in the latest grub
upgrade.
2/3) upgrading grub [###
