From: Chris Marusich <cmmarusich@gmail.com>
To: Benjamin Slade <beoram@gmail.com>
Cc: help-guix@gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: Re: LUKS-encrypted root and unencrypted /boot ?
Date: Sat, 04 Aug 2018 22:26:45 -0700 [thread overview]
Message-ID: <87wot5crje.fsf@gmail.com> (raw)
In-Reply-To: <87effef8u3.fsf@jnanam.net> (Benjamin Slade's message of "Sat, 04 Aug 2018 09:30:12 -0600")
[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]
Benjamin Slade <beoram@gmail.com> writes:
> I mused briefly about mirroring of the relevant things (kernels, initrd)
> from /gnu/store to /boot, but that's probably pretty hack-y.
The parts of GuixSD which require maintaining state outside of the store
tend to be a little complicated (in my opinion) because they don't fit
neatly into the "functional software deployment model" bubble that the
rest of Guix lives in.
We currently do this for the GRUB config: we copy it out of the store
into the /boot directory, instead of symlinking it. I believe this was
done in order to support the use case of putting /gnu/store and /boot on
different partitions. Technically, I think we could do the same sort of
thing for Linux kernel images and initrds, but what's the goal? If the
goal is just to make it so GRUB doesn't have to open the LUKS volume in
order to boot, then your solution already meets the goal.
However, since your solution puts all of /gnu/store in an unencrypted
partition, you should keep in mind that anything you put in the store
will also be unencrypted. Therefore, if you add anything from your home
directory to the store (e.g., by using local-file [see: (guix)
G-Expressions]), it may be exposed in the store. That said, since the
store is generally readable by everybody on the system (and remotely, if
you are using "guix publish"), one probably shouldn't be putting
sensitive information in the store to begin with.
Hope that helps!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-08-05 5:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 18:59 LUKS-encrypted root and unencrypted /boot ? Benjamin Slade
2018-08-02 6:59 ` Clément Lassieur
2018-08-03 17:05 ` Benjamin Slade
2018-08-03 18:53 ` Clément Lassieur
2018-08-04 15:30 ` Benjamin Slade
2018-08-04 15:48 ` Clément Lassieur
2018-08-04 21:14 ` Benjamin Slade
2018-08-05 5:26 ` Chris Marusich [this message]
2018-08-02 8:24 ` Chris Marusich
2018-08-03 17:07 ` Benjamin Slade
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=87wot5crje.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=beoram@gmail.com \
--cc=clement@lassieur.org \
--cc=help-guix@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.