unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: Richard Sent <richard@freakingpenguin.com>
Cc: help-guix@gnu.org
Subject: Re: Deferring evaluation of a get-secret procedure so -L doesn't evaluate it unless needed for build
Date: Fri, 5 Jan 2024 13:17:32 +0100	[thread overview]
Message-ID: <ZZfzXPjy9meNeNN2@ws> (raw)
In-Reply-To: <f6619a62a1ec2c710079a2a9fb286b9a@freakingpenguin.com>

[-- Attachment #1: Type: text/plain, Size: 766 bytes --]

Hi,

I cannot help you with your question, but completely unsolicited feedback
regarding this snippet:

On 2024-01-04 12:28:28 -0500, Richard Sent wrote:
> --8<---------------cut here---------------start------------->8---
> (define wireguard-lan-secret-service
>   (service
>    (wireguard-configuration
>     ...
>     (private-key
>      (plain-file "private.key"
>                  (get-secret*
>                   "System/WireGuard/LAN/private.key"))))))
> --8<---------------cut here---------------end--------------->8---

Storing secret keys in the store might not be the best idea, since they will be
world readable.

Have a nice day,
Tomas Volf

--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-01-05 12:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 17:28 Deferring evaluation of a get-secret procedure so -L doesn't evaluate it unless needed for build Richard Sent
2024-01-05 12:17 ` Tomas Volf [this message]

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=ZZfzXPjy9meNeNN2@ws \
    --to=~@wolfsden.cz \
    --cc=help-guix@gnu.org \
    --cc=richard@freakingpenguin.com \
    /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).