From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] C165: Fix ownership of suricata classification.config file.
Date: Tue, 15 Mar 2022 19:24:02 +0100 [thread overview]
Message-ID: <20220315182403.6359-1-stefan.schantl@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
The file has to be write-able for the WUI and update script, which both
are executed as nobody.
Fixes #12803.
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
---
config/rootfiles/core/165/update.sh | 3 +++
1 file changed, 3 insertions(+)
diff --git a/config/rootfiles/core/165/update.sh b/config/rootfiles/core/165/update.sh
index 00974de73..ffb552c80 100644
--- a/config/rootfiles/core/165/update.sh
+++ b/config/rootfiles/core/165/update.sh
@@ -129,6 +129,9 @@ ldconfig
telinit u
/etc/rc.d/init.d/firewall restart
+# Fix ownership of classification file.
+chown nobody:nobody /usr/share/suricata/classification.config
+
# Rebuild IPS rules
rm -vf /tmp/ids_page_locked
perl -e "require '/var/ipfire/ids-functions.pl'; &IDS::oinkmaster();"
--
2.30.2
next reply other threads:[~2022-03-15 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 18:24 Stefan Schantl [this message]
2022-03-19 22:00 ` Adolf Belka
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=20220315182403.6359-1-stefan.schantl@ipfire.org \
--to=stefan.schantl@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