From: Julien Lepiller <julien@lepiller.eu>
To: raingloom <raingloom@riseup.net>
Cc: 45911@debbugs.gnu.org
Subject: bug#45911: authorized-fields is not/badly documented
Date: Wed, 20 Jan 2021 16:15:01 -0500 [thread overview]
Message-ID: <A8B5F4CB-39B8-40B1-AC22-36B67ADFE27C@lepiller.eu> (raw)
In-Reply-To: <20210120213411.3420d912@riseup.net>
Le 20 janvier 2021 15:34:11 GMT-05:00, raingloom <raingloom@riseup.net> a écrit :
>On Sat, 16 Jan 2021 22:24:16 -0500
>Julien Lepiller <julien@lepiller.eu> wrote:
>
>> Actually, here's how I use it:
>>
>https://framagit.org/tyreunom/system-configuration/-/blob/master/systems/tachikoma.scm#L69
>>
>> And the key file is the one generated by guix, unmodified:
>>
>https://framagit.org/tyreunom/system-configuration/-/blob/master/keys/xana.pub
>>
>> Le 16 janvier 2021 19:34:49 GMT-05:00, raingloom
>> <raingloom@riseup.net> a écrit :
>> >On Sat, 16 Jan 2021 07:10:47 +0100
>> >Ricardo Wurmus <rekado@elephly.net> wrote:
>> >
>> >> raingloom <raingloom@riseup.net> writes:
>> >>
>> >> > guix archive --authorize started issuing a warning some time ago
>> >> > pointing to "authorized-keys" in "operating-system".
>> >> >
>> >> > * that is not a valid field of operating-system
>> >>
>> >> That’s right. It’s a field of guix-configuration, which is
>> >documented
>> >> in 10.8.1 Base Services.
>> >>
>> >
>> >Thanks, I found that out already, that's how I ran into the other
>> >issues.
>> >I'm still confused about what the proper way to store the config
>info
>> >is. Like how I should even store it as Scheme source code.
>
>Thanks, guess I'll go down the file route for now, but this is an
>unsatisfactory solution IMHO.
>What if you have multiple keys, or want to only include a subset of
>keys in a given machine?
>Having to use a file object to store a sexp is an odd choice when every
>other part of Guix tries as hard as it can to use sexps and Scheme data
>structures for configuration.
>
>If no one wants to fix it, mind if I give it a go?
Go ahead :)
next prev parent reply other threads:[~2021-01-20 21:16 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A8B5F4CB-39B8-40B1-AC22-36B67ADFE27C@lepiller.eu \
--to=julien@lepiller.eu \
--cc=45911@debbugs.gnu.org \
--cc=raingloom@riseup.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.