From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] ipblocklist: Ensure /var/ipfire/ipblocklist is owned and writable by "nobody"
Date: Mon, 22 Aug 2022 20:08:00 +0000 [thread overview]
Message-ID: <ddc5c786-2a77-03c6-dcdf-8ba7d349f8b1@ipfire.org> (raw)
In-Reply-To: <59c78fd9-46a7-6290-ad8e-cae28cfc2bfc@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]
Hello list,
today, Stefan reached out to me via phone and explained that /var/ipfire/ipblocklist/
should not be chown'ed to "nobody", since this would mean write access to the "sources"
file, a thing neither needed nor desirable.
Instead, he recommended touching a "modified" file in the same folder and granting
"nobody" write access to it. While testing, I noticed the same thing is necessary for
a "settings" file.
I will submit a second version of the patch in due course.
Best,
Peter Müller
> Fixes: #12917
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/rootfiles/core/170/update.sh | 3 +++
> lfs/ipblocklist-sources | 4 ++--
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/config/rootfiles/core/170/update.sh b/config/rootfiles/core/170/update.sh
> index b6b66f3f1..c7dc09946 100644
> --- a/config/rootfiles/core/170/update.sh
> +++ b/config/rootfiles/core/170/update.sh
> @@ -164,6 +164,9 @@ ldconfig
> mkdir -pv /var/lib/ipblocklist
> chown nobody:nobody /var/lib/ipblocklist
>
> +# Ensure permissions for /var/ipfire/ipblocklist are set properly
> +chown -Rv nobody:nobody /var/ipfire/ipblocklist
> +
> # Rebuild fcrontab from scratch
> /usr/bin/fcrontab -z
>
> diff --git a/lfs/ipblocklist-sources b/lfs/ipblocklist-sources
> index 30b9e94a4..87bd95cca 100644
> --- a/lfs/ipblocklist-sources
> +++ b/lfs/ipblocklist-sources
> @@ -47,7 +47,7 @@ b2 :
>
> $(TARGET) :
> @$(PREBUILD)
> - mkdir -p /var/ipfire/ipblocklist
> - install -v -m 0644 $(DIR_SRC)/config/ipblocklist/sources /var/ipfire/ipblocklist
> + install -d -o nobody -g nobody -m 0755 /var/ipfire/ipblocklist
> + install -v -o nobody -g nobody -m 0644 $(DIR_SRC)/config/ipblocklist/sources /var/ipfire/ipblocklist
>
> @$(POSTBUILD)
next prev parent reply other threads:[~2022-08-22 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 6:30 Peter Müller
2022-08-22 8:00 ` Bernhard Bitsch
2022-08-22 20:08 ` Peter Müller [this message]
2022-08-22 20:11 ` [PATCH v2] ipblocklist: Both "settings" and "modify" need to be writable for "nobody" Peter Müller
2022-08-25 15:49 ` Michael Tremer
2022-09-01 20:34 ` Peter Müller
2022-08-22 21:03 ` [PATCH] ipblocklist: Ensure /var/ipfire/ipblocklist is owned and writable by "nobody" Rob Brewer
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=ddc5c786-2a77-03c6-dcdf-8ba7d349f8b1@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/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