From: Josselin Poiret <dev@jpoiret.xyz>
To: Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br>,
guix-devel <guix-devel@gnu.org>
Subject: Re: secure boot
Date: Tue, 23 Aug 2022 09:42:35 +0200 [thread overview]
Message-ID: <87h723v21g.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87a67wrq81.fsf@yahoo.com.br>
Hi Antonio,
Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br> writes:
> 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?
This subject has been discussed a bit in the past. My opinion on what
you're suggesting is that:
* We should not modify the store in place. This is bound to create problems
for the user, because we'd be breaking the Guix guarantees.
* You could sign it out of the store. Basically, something like `sign
/gnu/store/xxxxxx-bzImage > /boot/bzImage_signed`. However, this poses
problems with generations, since either we prohibit loading older
generations, which is a huge step backwards, or we sign all of the older
generations as well, which will take a non-negligible amount of space.
In that case, we'd also need to keep track of the different signed
kernels that are sitting in /boot to be able to clean them up when the
generations are deleted.
It's not an easy problem unfortunately, and the number of people whose
threat model requires such a thing is slim, hence the lack of work in
that direction.
Best,
--
Josselin Poiret
next prev parent reply other threads:[~2022-08-23 7:55 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 [this message]
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=87h723v21g.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 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.