On 22.01.19 07:35, Michael Chang wrote:
> On Fri, Jan 11, 2019 at 08:49:28PM +0100, Alexander Graf wrote:
>>
>>
>> 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
>
On Fri, Jan 11, 2019 at 08:49:28PM +0100, Alexander Graf wrote:
>
>
> 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 k
On Mon, Jan 14, 2019 at 01:42:29PM -0500, Peter Jones wrote:
> On Mon, Jan 14, 2019 at 05:14:21PM +0800, Michael Chang wrote:
> > > > 3. The Shim's fallback mode has been used to recreate boot entries after
> > > > firmware update for x86, not sure if that any problem for ARM.
> > >
> > > It thoug
On Mon, Jan 14, 2019 at 11:22:23AM +0100, Alexander Graf wrote:
> On 01/14/2019 10:14 AM, Michael Chang wrote:
> > On Mon, Jan 14, 2019 at 08:07:34AM +0100, Ard Biesheuvel wrote:
> > > On Mon, 14 Jan 2019 at 05:58, Michael Chang wrote:
> > > > On Fri, Jan 11, 2019 at 10:58:54AM +, Leif Lindhol
On Mon, Jan 14, 2019 at 05:14:21PM +0800, Michael Chang wrote:
> > > 3. The Shim's fallback mode has been used to recreate boot entries after
> > > firmware update for x86, not sure if that any problem for ARM.
> >
> > It thought fallback was a separate binary? If the distros sign that,
> > there
On Mon, Jan 14, 2019 at 08:07:34AM +0100, Ard Biesheuvel wrote:
> > 3. The Shim's fallback mode has been used to recreate boot entries
> > after firmware update for x86, not sure if that any problem for ARM.
>
> It thought fallback was a separate binary? If the distros sign that,
> there is no rea
On Mon, Jan 14, 2019 at 10:57:10AM +0100, Ard Biesheuvel wrote:
> On Mon, 14 Jan 2019 at 10:53, Michael Chang wrote:
> >
> > On Mon, Jan 14, 2019 at 08:41:21AM +0100, Ard Biesheuvel wrote:
> > > On Mon, 14 Jan 2019 at 08:30, Michael Chang wrote:
> > > >
> > > > On Fri, Jan 11, 2019 at 03:17:54PM
On 01/11/2019 11:58 AM, 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 community, we are driving to the world of UEFI
On 01/14/2019 10:14 AM, Michael Chang wrote:
On Mon, Jan 14, 2019 at 08:07:34AM +0100, Ard Biesheuvel wrote:
On Mon, 14 Jan 2019 at 05:58, Michael Chang wrote:
On Fri, Jan 11, 2019 at 10:58:54AM +, Leif Lindholm wrote:
On Thu, Jan 10, 2019 at 09:59:38AM +0100, Alexander Graf wrote:
Am 10
On Mon, 14 Jan 2019 at 10:53, Michael Chang wrote:
>
> On Mon, Jan 14, 2019 at 08:41:21AM +0100, Ard Biesheuvel wrote:
> > On Mon, 14 Jan 2019 at 08:30, Michael Chang wrote:
> > >
> > > On Fri, Jan 11, 2019 at 03:17:54PM +0100, Ard Biesheuvel wrote:
> > > > On Fri, 11 Jan 2019 at 11:58, Leif Lind
On Mon, Jan 14, 2019 at 08:41:21AM +0100, Ard Biesheuvel wrote:
> On Mon, 14 Jan 2019 at 08:30, Michael Chang wrote:
> >
> > On Fri, Jan 11, 2019 at 03:17:54PM +0100, Ard Biesheuvel wrote:
> > > On Fri, 11 Jan 2019 at 11:58, Leif Lindholm
> > > wrote:
> > > >
> > > > On Thu, Jan 10, 2019 at 09:5
On Mon, Jan 14, 2019 at 08:07:34AM +0100, Ard Biesheuvel wrote:
> On Mon, 14 Jan 2019 at 05:58, Michael Chang wrote:
> >
> > On Fri, Jan 11, 2019 at 10:58:54AM +, Leif Lindholm wrote:
> > > On Thu, Jan 10, 2019 at 09:59:38AM +0100, Alexander Graf wrote:
> > > > > Am 10.01.2019 um 09:12 schrieb
On Mon, 14 Jan 2019 at 08:30, Michael Chang wrote:
>
> On Fri, Jan 11, 2019 at 03:17:54PM +0100, Ard Biesheuvel wrote:
> > 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 M
On Fri, Jan 11, 2019 at 03:17:54PM +0100, Ard Biesheuvel wrote:
> 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
On Mon, 14 Jan 2019 at 05:58, Michael Chang wrote:
>
> On Fri, Jan 11, 2019 at 10:58:54AM +, 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 ne
On Fri, Jan 11, 2019 at 10:58:54AM +, 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 g
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
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 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
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
> 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, almost ..
>
> There is a missing piece in the puzzle remaining, that is boot
21 matches
Mail list logo