From: Peter Korsgaard <peter@korsgaard.com>
To: Jens Maus via buildroot <buildroot@buildroot.org>
Cc: Bernd Kuhls <bernd@kuhls.net>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
Jens Maus <mail@jens-maus.de>
Subject: Re: [Buildroot] [PATCH v2] package/nut: package/nut: specify --with-user/group when building NUT
Date: Tue, 26 Sep 2023 10:02:46 +0200 [thread overview]
Message-ID: <87y1gtuztl.fsf@48ers.dk> (raw)
In-Reply-To: <20230923165214.4014466-1-mail@jens-maus.de> (Jens Maus via buildroot's message of "Sat, 23 Sep 2023 18:52:14 +0200")
>>>>> "Jens" == Jens Maus via buildroot <buildroot@buildroot.org> writes:
> This commit fixes a problem where the NUT package couldn't be
> used as a NUT server due to the fact that the default group for
> nobody is "nogroup" and not "nobody" like the internal default
> of NUT. Thus, when starting a NUT server daemon the daemon starts
> with incorrect group permissions. This commit fixes this
> shortcoming by introducing a dedicated 'nut' user and 'nut' group
> to drop priviledges to it.
> Signed-off-by: Jens Maus <mail@jens-maus.de>
> ---
> Changes v1 -> v2:
> - added NUT_USERS with nut/nut user and group (Yann)
> Signed-off-by: Jens Maus <mail@jens-maus.de>
Committed to 2023.02.x, 2023.05.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-26 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 15:35 [Buildroot] [PATCH 2/2] package/nut: specify --with-user/group when building NUT Jens Maus
2017-06-08 19:20 ` Yann E. MORIN
2017-06-10 7:04 ` Jens Maus
2017-06-10 7:21 ` Yann E. MORIN
2023-09-23 16:52 ` [Buildroot] [PATCH v2] package/nut: " Jens Maus via buildroot
2023-09-23 20:31 ` Yann E. MORIN
2023-09-26 8:02 ` Peter Korsgaard [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=87y1gtuztl.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=mail@jens-maus.de \
--cc=yann.morin.1998@free.fr \
/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 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.