Re: last preparations for switching to production Secure Boot key

2019-03-10 Thread Ben Hutchings
On Tue, 2019-02-26 at 21:23 +0100, Ansgar wrote: > Hi, > > Colin Watson writes: > > On Mon, Feb 25, 2019 at 08:13:22PM +0100, Ansgar wrote: > > > I added support for listing `trusted_certs`[1] as proposed by Ben > > > Hutchings. This means the `files.json` structure *must* list the > > > sha256su

Re: last preparations for switching to production Secure Boot key

2019-02-26 Thread Ansgar
Hi, Colin Watson writes: > On Mon, Feb 25, 2019 at 08:13:22PM +0100, Ansgar wrote: >> I added support for listing `trusted_certs`[1] as proposed by Ben >> Hutchings. This means the `files.json` structure *must* list the >> sha256sum of certificates the signed binaries will trust (this can be an >

Re: last preparations for switching to production Secure Boot key

2019-02-26 Thread Colin Watson
On Mon, Feb 25, 2019 at 08:13:22PM +0100, Ansgar wrote: > I added support for listing `trusted_certs`[1] as proposed by Ben > Hutchings. This means the `files.json` structure *must* list the > sha256sum of certificates the signed binaries will trust (this can be an > empty list in case no hard-cod

last preparations for switching to production Secure Boot key

2019-02-25 Thread Ansgar
Hi, I added support for listing `trusted_certs`[1] as proposed by Ben Hutchings. This means the `files.json` structure *must* list the sha256sum of certificates the signed binaries will trust (this can be an empty list in case no hard-coded certificates are trusted). I would like to implement on