On Thu, Jan 10, 2019 at 09:59:38AM +0100, Alexander Graf wrote:
> > Am 10.01.2019 um 09:12 schrieb Michael Chang :
> >
> > Hi,
> >
> > With the advent of new verifier framework and shim lock protocol support
> > to the grub's community, we are driving to the world of UEFI Secure
> > Boot, well, a
Just re-pinging on this ...
P.
On 1/4/19 7:53 AM, Prarit Bhargava wrote:
> Please be aware I am NOT subscribed to grub-devel.
>
> P.
>
> ---8<---
>
> Customers and users of the kernel are commenting that there is no way to
> update
> a grub variable without copy and pasting the existing dat
On Fri, 11 Jan 2019 at 11:58, Leif Lindholm wrote:
>
> On Thu, Jan 10, 2019 at 09:59:38AM +0100, Alexander Graf wrote:
> > > Am 10.01.2019 um 09:12 schrieb Michael Chang :
> > >
> > > Hi,
> > >
> > > With the advent of new verifier framework and shim lock protocol support
> > > to the grub's commu
From: Andrei Borzenkov
This patch adds support for native DHCPv4 and removes requirement for
BOOTP compatibility support in DHCP server.
There is no provision for selecting preferred server. We take the first
OFFER and try to REQUEST configuration from it. If NAK was received,
transaction is res
On Thu, Jan 10, 2019 at 12:59 AM Alexander Graf wrote:
> So really dumb question here: What if we didn't use the MS key? What if
> instead, we just provide a SUSE/openSUSE key and give customers the ability
> to sign their own grub+Linux binaries?
Then you end up blocking install of any Linux d
On 11.01.19 20:32, Matthew Garrett wrote:
> On Thu, Jan 10, 2019 at 12:59 AM Alexander Graf wrote:
>> So really dumb question here: What if we didn't use the MS key? What if
>> instead, we just provide a SUSE/openSUSE key and give customers the ability
>> to sign their own grub+Linux binaries
