From: Josselin Poiret <dev@jpoiret.xyz>
To: Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br>,
guix-devel@gnu.org
Subject: Re: secure boot
Date: Sun, 21 Aug 2022 10:46:51 +0200 [thread overview]
Message-ID: <87pmguugp0.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87h727tazd.fsf@yahoo.com.br>
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.
> In this context, can I assume that the risk of not having secure boot is
> minimized by the fact that in each system reconfiguration, the early
> boot chain is overwritten is such a way that, if a malicious is
> introduced somehow, it will be also overwritten? Am I correct?
A reconfigure would overwrite the bootloader, and most likely create a
new system generation with bootloader configuration.
> In addition, how much more difficult it is to introduce such malicious
> code in a Guix system giving its functional approach and store system?
> (in comparison with others Linux distributions).
Nothing is stopping an attacker from overwriting your bootloader with
their own, which could load a kernel of their choosing. They would need
to be able to boot off something though. And once you're compromised
that way, I don't think you could consider running `guix system
reconfigure` an option.
Best,
--
Josselin Poiret
next prev parent reply other threads:[~2022-08-21 8:47 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 [this message]
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
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=87pmguugp0.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=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 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).