From: raingloom <raingloom@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 45911@debbugs.gnu.org
Subject: bug#45911: authorized-fields is not/badly documented
Date: Mon, 25 Jan 2021 18:15:43 +0100 [thread overview]
Message-ID: <20210125181543.7f16e903@riseup.net> (raw)
In-Reply-To: <87y2gkj9xk.fsf@elephly.net>
On Sat, 23 Jan 2021 10:10:15 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:
> raingloom <raingloom@riseup.net> writes:
>
> > Okay, so I figured out that I should use a G-Expression if I want to
> > compute the file, instead of just include it. Still not sure how to
> > store it as Scheme data, but I have an untested idea involving the
> > "pipe" syntax for symbols.
>
> Use computed-file instead of local-file.
>
I know about computed-file, the issue is that the syntax of the key is
not strictly Scheme. The long hexadecimal block isn't parsed as a
number:
```
(with-input-from-file "/etc/guix/signing-key.pub" read)
...
/etc/guix/signing-key.pub:4:8: Unknown # object: #\C
```
Trying to store it as a module results in the same error.
So I can't just have an associative list of hostnames and signing keys
and filter it based on the hostname, I have to store each key as an
opaque file, completely bypassing the module system.
next prev parent reply other threads:[~2021-01-25 23:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 3:16 bug#45911: authorized-fields is not/badly documented raingloom
2021-01-16 6:10 ` Ricardo Wurmus
2021-01-17 0:34 ` raingloom
2021-01-17 3:17 ` Julien Lepiller
2021-01-17 3:24 ` Julien Lepiller
2021-01-20 20:34 ` raingloom
2021-01-20 21:15 ` Julien Lepiller
2021-01-20 8:49 ` Ludovic Courtès
2021-01-23 5:39 ` raingloom
2021-01-23 9:10 ` Ricardo Wurmus
2021-01-25 17:15 ` raingloom [this message]
2021-01-26 7:13 ` Ricardo Wurmus
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=20210125181543.7f16e903@riseup.net \
--to=raingloom@riseup.net \
--cc=45911@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).