From: "Ludovic Courtès" <ludo@gnu.org>
To: Josua Stingelin <josuast@hotmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Changing permissions of files created with simple-service etc-service-type
Date: Mon, 14 Feb 2022 22:48:09 +0100 [thread overview]
Message-ID: <87czjpqfvq.fsf@gnu.org> (raw)
In-Reply-To: <DB9PR06MB76571332BB16351FEE980C66AA309@DB9PR06MB7657.eurprd06.prod.outlook.com> (Josua Stingelin's message of "Fri, 11 Feb 2022 12:25:23 +0100")
Josua Stingelin <josuast@hotmail.com> skribis:
> I'm using the etc-service-type of the simple-service to copy the file. Which
> works great. But sadly grants read-access to everyone. I'd prefer it only be
> readable by root.
>
> (simple-service 'wpasupplicantconf-service
> etc-service-type
> `(("wpa_supplicant.conf",
> (local-file "wpa_supplicant.conf"))))
>
> $ ls -l /etc/wpa_supplicant.conf
> -r--r--r-- 1 root root 2.3K Feb 11 11:39 /etc/wpa_supplicant.conf
>
> How can I achieve that?
Currently ‘etc-service-type’ does not let you specify permissions. All
the files that end up in /etc first go through the store though, so
changing the permission of those files once copied under /etc wouldn’t
buy you much in terms of confidentiality. For example, there’s a copy
of ‘wpa_supplicant.conf’ above in your store. For that reason, files
containing secrets must be handled “out of band”, without Guix support.
I guess changing permissions for /etc could still be useful for those
programs that verify permission bits and refuse to start if the config
file is readable by all. However, those programs may have a good reason
to verify that, so…
Thoughts?
Ludo’.
next prev parent reply other threads:[~2022-02-14 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 11:25 Changing permissions of files created with simple-service etc-service-type Josua Stingelin
2022-02-14 21:48 ` Ludovic Courtès [this message]
2022-02-16 15:41 ` Josua Stingelin
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=87czjpqfvq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=josuast@hotmail.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 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.