From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Timo Wilken <guix@twilken.net>
Cc: help-guix@gnu.org
Subject: Re: How do I install a file with custom permissions?
Date: Tue, 29 Nov 2022 20:34:44 +0100 [thread overview]
Message-ID: <87wn7dee8c.fsf@nckx> (raw)
In-Reply-To: <20221129192413.q75rkyevtrtslyix@timo-pc>
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
Hi Timo,
Timo Wilken 写道:
> I'm trying to patch the `wireguard-service-type' to accept
> pre-shared
> keys and add them to the generated config. This all seems to
> work
> fine, except that I can't get guix to generate a
> non-world-readable
> configuration file.
Alas (for your plans), this is not possible. Guix's store model,
inherited from Nix, is a word-readable heap.
Dealing with secrets outside of the store is one area where Nix is
‘ahead’ of Guix, in that they seem to have multiple solutions[0].
Very Nix.
Guix users currently use strategies similar to the second half of
that table: the secret is placed outside of the store, not managed
through Guix, and the Guix service/package is pointed to it at run
time. Every search result for ‘secrets’ in the Guix manual is
part of such a primitive scheme.
This is how Wireguard is set up on berlin, the Guix build farm.
/etc/wireguard/private.key was generated manually and Guix never
deals with it.
If you want to add secrets to Guix services, you'll have to design
a general mechanism for doing so first. I don't have links handy
but I'm sure there's prior discussion, perhaps even art, on the
mailing lists.
Sorry,
T G-R
[0]: https://nixos.wiki/wiki/Comparison_of_secret_managing_schemes
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-11-29 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 19:24 How do I install a file with custom permissions? Timo Wilken
2022-11-29 19:34 ` Julien Lepiller
2022-11-29 19:43 ` Timo Wilken
2022-11-29 19:34 ` Tobias Geerinckx-Rice [this message]
2022-11-29 20:56 ` Timo Wilken
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=87wn7dee8c.fsf@nckx \
--to=me@tobias.gr \
--cc=guix@twilken.net \
--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.
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).