From: Arun Isaac <arunisaac@systemreboot.net>
To: Nathan Dehnel <ncdehnel@gmail.com>,
Gary Johnson <lambdatronic@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: How to put a file in /gnu/store and set its permissions
Date: Wed, 08 Dec 2021 11:32:41 +0530 [thread overview]
Message-ID: <87v8zzws5a.fsf@systemreboot.net> (raw)
In-Reply-To: <CAEEhgEvt9N_1gDr_6t6_C+pFOfmap2P0KCk1pD29GC3mBqY8hQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
> by the looks of it, would still be putting the key in the store, which
> is insecure.
That's correct. I think you should look at how the ssh service or the
wireguard service manages its keys. IIRC, they do so by generating a new
key during /activation/ of the system.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 524 bytes --]
next prev parent reply other threads:[~2021-12-08 6:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 22:47 How to put a file in /gnu/store and set its permissions Nathan Dehnel
2021-12-05 5:12 ` Leo Famulari
2021-12-05 21:18 ` Nathan Dehnel
2021-12-06 2:30 ` Gary Johnson
2021-12-08 0:59 ` Nathan Dehnel
2021-12-08 6:02 ` Arun Isaac [this message]
2021-12-08 16:26 ` Gary Johnson
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=87v8zzws5a.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=help-guix@gnu.org \
--cc=lambdatronic@disroot.org \
--cc=ncdehnel@gmail.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).