On Fri, Aug 17, 2018 at 4:42 PM Colin Watson wrote:
>
> On Fri, Aug 17, 2018 at 03:26:36PM +0200, Somebody else wrote:
> > Now, MY setup, which worked up to grub-efi 2.02+dfsg1-4, was such that
> > I removed all Microsoft-owned keys from my system and replaced them
> >
On Fri, Aug 17, 2018 at 2:25 PM Ian Campbell wrote:
>
> On Fri, 2018-08-17 at 10:22 +0200, Somebody else wrote:
> > Any pointers?
>
> Have you seen https://wiki.debian.org/SecureBoot ? I'm not involved in
> that effort but AIUI it describes the plan for what (and wh
So my current state of the investigation is:
Debian broke the, in my opinion, perfectly reasonable boot flow of
UEFI -> Signed Standalone GRUB -> GPG-signed Kernel
in favor of requiring the "shim" (packages: shim and shim-signed).
This has been done by requiring the Shim protocol. The patch
Hi,
so reading the source code of the debian/patches included in the
latest package and enabling additional debug logging (linux and
linuxefi, specifically) yielded additional information. It seems that
my setup is now broken because the defaults were changed to require
the "shim protocol". My
Package: grub-efi
Version: 2.02+dfsg1-5
Severity: grave Justification: renders package unusable
Dear Maintainer,
I use Debian Buster with secureboot turned on on my Dell XPS13. I replaced
all UEFI keys with my own RSA keys and created a standalone grub_efi using
the scripts at
5 matches
Mail list logo
