From: Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: secure boot
Date: Mon, 22 Aug 2022 22:13:50 +0200 [thread overview]
Message-ID: <87a67wrq81.fsf@yahoo.com.br> (raw)
In-Reply-To: <87pmguugp0.fsf@jpoiret.xyz> (Josselin Poiret's message of "Sun, 21 Aug 2022 10:46:51 +0200")
Thank you for your answer!
Josselin Poiret <dev@jpoiret.xyz> writes:
> 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.
>
Can we imagine signing the kernel outside the guix layer, I mean,
directly into the store without using guix commands? I understand this
would break conceptually the Guix functional characterization, and it is
not very "clean". But despite these points, any other side effects expected?
I'm not sure if my question is convenient for this list, if it is not,
sorry for the inconvenience.
Best regards,
--
Antonio Carlos PADOAN JUNIOR
GPG fingerprint:
243F 237F 2DD3 4DCA 4EA3 1341 2481 90F9 B421 A6C9
next prev parent reply other threads:[~2022-08-22 20:14 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 [this message]
2022-08-23 7:42 ` Josselin Poiret
2022-08-23 18:32 ` Antonio Carlos Padoan Junior
2022-08-24 3:07 ` Philip McGrath
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a67wrq81.fsf@yahoo.com.br \
--to=acpadoanjr@yahoo.com.br \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.