From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: development@lists.ipfire.org
Subject: Re: [PATCH] backup.pl: Create the new unbound user and group when doing a restore
Date: Mon, 11 May 2026 18:57:56 +0100 [thread overview]
Message-ID: <48BAC698-D306-47E7-8B0E-7E6C75E50B42@ipfire.org> (raw)
In-Reply-To: <20260511165551.197587-1-adolf.belka@ipfire.org>
Hello Adolf,
Thanks for the patch, but I am not sure whether we strictly need it. Maybe we need it for a reason I am not aware of.
So if someone restores a backup from an older version, the new user should already exist as we create it in the updater. Nothing to do during the restore. If someone is taking a backup created on c202 and takes it back to lets say c199, then there is no Unbound user and the files have the wrong ownership but there is nothing we can do about it.
All the best,
-Michael
> On 11 May 2026, at 17:55, Adolf Belka <adolf.belka@ipfire.org> wrote:
>
> - With the introduction of the unbound user and group, when a restore is done from a
> earlier backup when user and group nobody were used then the unbound user and group
> are removed as passwd and group are backed up.
> - Using the entry already present for the dhcpcd user and group I cre4ated this patch.
> - Not 100% certain it is the correct way to do it, as I am not sure about if a restore
> is done where the unbound user and group already exist but presumably the same effect
> occurs with the dhcpcd user and group.
>
> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
> ---
> config/backup/backup.pl | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/config/backup/backup.pl b/config/backup/backup.pl
> index 9a54b50d3..8dd77b3ee 100644
> --- a/config/backup/backup.pl
> +++ b/config/backup/backup.pl
> @@ -108,6 +108,14 @@ restore_backup() {
> -s /bin/false \
> -u 52 dhcpcd
>
> + # create unbound user
> + groupadd -g 103 unbound
> + useradd -c 'unbound User' \
> + -d /var/empty \
> + -g unbound \
> + -s /bin/false \
> + -u 103 unbound
> +
> # Run converters
>
> # Outgoing Firewall
> --
> 2.54.0
>
>
prev parent reply other threads:[~2026-05-11 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 16:55 Adolf Belka
2026-05-11 17:57 ` Michael Tremer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48BAC698-D306-47E7-8B0E-7E6C75E50B42@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=adolf.belka@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