From: Jan Nieuwenhuizen <janneke@gnu.org>
To: 39819@debbugs.gnu.org
Cc: maxim.cournoyer@gmail.com
Subject: bug#39819: [PATCH 1/2] services: guix: Make /etc/guix/acl really declarative by default.
Date: Sun, 25 Oct 2020 06:59:08 +0100 [thread overview]
Message-ID: <87y2ju9783.fsf@gnu.org> (raw)
In-Reply-To: <87tuujgr23.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 25 Oct 2020 01:08:52 +0200")
Ludovic Courtès writes:
Hello,
> I went ahead and pushed this as c6ef627c97e5e6a94688baf20892ae3429f86897
> with the changes below, accounting for Vagrant’s comment and for the
> fact that childhurds rely on the non-declarative behavior (which hadn’t
> occurred to me before), as well as fixing other typos.
>
>
> + ;; By default, the secret service introduces a pre-initialized
> + ;; /etc/guix/acl file in the childhurd. Thus, clear
> + ;; 'authorize-key?' so that it's not overridden at activation
> + ;; time.
> + (modify-services %base-services/hurd
> + (guix-service-type config =>
> + (guix-configuration
> + (inherit config)
> + (authorize-key? #f))))))))
Ah, good catch!
Janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2020-10-25 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 4:30 bug#39819: guix-service-type authorized keys are not honored when /etc/guix/acl exists Maxim Cournoyer
2020-02-28 4:32 ` Maxim Cournoyer
[not found] ` <87v9fhf3my.fsf@inria.fr>
2020-10-11 11:00 ` bug#39819: Declarative /etc/guix/acl? Efraim Flashner
[not found] ` <87k0vxaumm.fsf@gnu.org>
2020-10-12 12:53 ` Ludovic Courtès
[not found] ` <20201021150823.20508-1-ludo@gnu.org>
2020-10-21 15:08 ` bug#39819: [PATCH 2/2] doc: Add "Getting Substitutes from Other Servers" section Ludovic Courtès
[not found] ` <87tuujgr23.fsf@gnu.org>
2020-10-25 5:59 ` Jan Nieuwenhuizen [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=87y2ju9783.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=39819@debbugs.gnu.org \
--cc=maxim.cournoyer@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.
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).