From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: help-guix@gnu.org
Subject: Re: Another service definition question: Files containing secrets?
Date: Mon, 29 Jul 2024 17:38:31 +0200 [thread overview]
Message-ID: <99677080-16c8-4e20-ba7f-063a908272a5@crazy-compilers.com> (raw)
In-Reply-To: <f1ee1cfd-4e4a-41d9-9fdc-d81662abfa65@app.fastmail.com>
Hi,
Am 28.07.24 um 23:27 schrieb Zack Weinberg:
> The*problem* with this is that it appears there's no way to make a file
> in the store not be world readable.
>
> What's the best way to deal with this situation?
I feel your pain! Several years ago already I started a nullmailer
service for Guix - and never finished it for similar reasons.
(nullmailer expects the password being part of the config file.)
I'm afraid, the only solution is to create a service which generates the
config at boot time from a file containing the password and some
template (or guile data structure). The password file would not be part
of the Guix system definition. Anyhow I'm not aware of any example, sorry.
Please let me know if you implement something like this as I'd like to
eventally finish the nullmailer service :-)
--
Regards
Hartmut Goebel
| Hartmut Goebel |h.goebel@crazy-compilers.com |
|www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2024-07-29 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 21:27 Another service definition question: Files containing secrets? Zack Weinberg
2024-07-29 15:38 ` Hartmut Goebel [this message]
2024-08-03 9:09 ` Marek Paśnikowski
2024-07-29 23:33 ` Giacomo via
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=99677080-16c8-4e20-ba7f-063a908272a5@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--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).