unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Philip McGrath" <philip@philipmcgrath.com>
To: "Josselin Poiret" <dev@jpoiret.xyz>,
	"Antonio Carlos Padoan Junior" <acpadoanjr@yahoo.com.br>,
	"Brian Cully" <guix-devel@gnu.org>
Subject: Re: secure boot
Date: Tue, 23 Aug 2022 23:07:26 -0400	[thread overview]
Message-ID: <d49e7ac5-805b-4d08-ac33-61b3e3a9e27b@www.fastmail.com> (raw)
In-Reply-To: <87pmguugp0.fsf@jpoiret.xyz>

On Sun, Aug 21, 2022, at 4:46 AM, Josselin Poiret wrote:
> Hi Antonio,
>
> Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br> writes:
>
>> As far as I understand, Guix doesn't provide means to automatically sign
>> bootloaders and kernels in order to use UEFI secure boot after each system
>> reconfigure (assuming a PKI is properly implemented).  Hence, using
>> secure boot with Guix is currently not viable (am i correct?).
>
> You're right, we don't really have any means to do that.  It would have
> to be done outside of the store, again, so that the private key doesn't
> leak into it.
>

I could imagine a process like this:

 1. Build the binary that needs to be signed.
 2. Outside of the Guix build environment, create a detached signature
    for the binary using your secret key.
 3. Add the detached signature to the Guix store, perhaps with 'local-file'.
 4. Use Guix to attach the signature to the built binary.
 5. Use the signed binary in your operating-system configuration.

IIUC, executables that run in the UEFI environment need "secure boot" signatures to be attached, but you may be able to use detached signatures directly for other things that they want to verify by means other than "secure boot".

I expect the things that need to be signed are small, build reproducibly, and change rarely, which might make this especially practical.

-Philip


  parent reply	other threads:[~2022-08-24  3:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87h727tazd.fsf.ref@yahoo.com.br>
2022-08-20 11:23 ` secure boot Antonio Carlos Padoan Junior
2022-08-20 12:18   ` Tobias Platen
2022-08-21  8:46   ` Josselin Poiret
2022-08-22 20:13     ` Antonio Carlos Padoan Junior
2022-08-23  7:42       ` Josselin Poiret
2022-08-23 18:32         ` Antonio Carlos Padoan Junior
2022-08-24  3:07     ` Philip McGrath [this message]
2022-08-24 17:24       ` Maxime Devos
     [not found] <mailman.77.1661011233.4812.guix-devel@gnu.org>
2022-08-20 19:11 ` kiasoc5

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d49e7ac5-805b-4d08-ac33-61b3e3a9e27b@www.fastmail.com \
    --to=philip@philipmcgrath.com \
    --cc=acpadoanjr@yahoo.com.br \
    --cc=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).