unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Zack Weinberg" <zack@owlfolio.org>
To: help-guix@gnu.org
Subject: Another service definition question: Files containing secrets?
Date: Sun, 28 Jul 2024 17:27:00 -0400	[thread overview]
Message-ID: <f1ee1cfd-4e4a-41d9-9fdc-d81662abfa65@app.fastmail.com> (raw)

The same slightly weird daemon I was talking about earlier expects to
find another file in /etc containing a piece of secret information - namely,
a token it will use to authenticate to a remote server.  This token does
not change in normal operation, and the most natural way to deal with it
would be to provide it as part of the service configuration.  (It cannot
be generated at activation time, the way SSH host keys are.)

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?

zw


             reply	other threads:[~2024-07-28 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-28 21:27 Zack Weinberg [this message]
2024-07-29 15:38 ` Another service definition question: Files containing secrets? Hartmut Goebel
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=f1ee1cfd-4e4a-41d9-9fdc-d81662abfa65@app.fastmail.com \
    --to=zack@owlfolio.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.
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).