From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [RFC PATCH] backup: Set owner of /var/ipfire/backup/{in, ex}clude to "root"
Date: Sat, 17 Sep 2022 10:17:07 +0000 [thread overview]
Message-ID: <5563a19f-545d-c6c3-2634-c49e426276c1@ipfire.org> (raw)
In-Reply-To: <3E4A3080-E33E-4EB9-B431-746D8D3C78FA@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2760 bytes --]
Hello Michael,
thanks for your reply. Indeed, glad you caught that.
Before I submit a second version: Shouldn't the {in,ex}clude.user files also be owned
by root? I was unable to find any instance in the source code where these are modified
by an unprivileged user.
On that note, is it intended/desired that many subfolders of /var/ipfire/ are owned
by "nobody"? While I of course see the need for "nobody" to write _files_, do not quite
get why the parent folders (such as /var/ipfire/auth/, /var/ipfire/ca/, etc. pp.) have
to be owned by that user as well.
Thanks, and best regards,
Peter Müller
> Hello Peter,
>
> I agree that the files should be owned by root. However, your patch doesn’t fix that.
>
>> On 15 Sep 2022, at 21:15, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
>> Since these files are static, there is no legitimate reason why they
>> should be owned (hence writable) by "nobody".
>>
>> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
>> ---
>> lfs/backup | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/lfs/backup b/lfs/backup
>> index 6f686bf22..adbf16e65 100644
>> --- a/lfs/backup
>> +++ b/lfs/backup
>> @@ -1,7 +1,7 @@
>> ###############################################################################
>> # #
>> # IPFire.org - A linux based firewall #
>> -# Copyright (C) 2007-2021 IPFire Team <info(a)ipfire.org> #
>> +# Copyright (C) 2007-2022 IPFire Team <info(a)ipfire.org> #
>> # #
>> # This program is free software: you can redistribute it and/or modify #
>> # it under the terms of the GNU General Public License as published by #
>> @@ -61,8 +61,8 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
>> @$(PREBUILD)
>> -mkdir -p /var/ipfire/backup/bin
>> install -v -m 755 -o root $(DIR_SRC)/config/backup/backup.pl /var/ipfire/backup/bin
>> - install -v -m 644 $(DIR_SRC)/config/backup/include /var/ipfire/backup/
>> - install -v -m 644 $(DIR_SRC)/config/backup/exclude /var/ipfire/backup/
>> + install -v -m 644 -o root $(DIR_SRC)/config/backup/include /var/ipfire/backup/
>> + install -v -m 644 -o root $(DIR_SRC)/config/backup/exclude /var/ipfire/backup/
>
> They have been created as root before. That is the default.
>
>> chown nobody:nobody -R /var/ipfire/backup/
>
> And here is where they will be changed. Still.
>
>> chown root:root -R /var/ipfire/backup/bin/
>> -mkdir -p /var/ipfire/backup/addons
>> --
>> 2.35.3
>
> -Michael
next prev parent reply other threads:[~2022-09-17 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 19:15 [RFC PATCH] backup: Set owner of /var/ipfire/backup/{in,ex}clude " Peter Müller
2022-09-16 8:27 ` [RFC PATCH] backup: Set owner of /var/ipfire/backup/{in, ex}clude " Michael Tremer
2022-09-17 10:17 ` Peter Müller [this message]
2022-09-18 9:17 ` Michael Tremer
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=5563a19f-545d-c6c3-2634-c49e426276c1@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