From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8b981e4d76fcb9d380ae1cbd4c9eeec1726e593e
Date: Fri, 05 Apr 2024 20:29:55 +0000 [thread overview]
Message-ID: <4VB98M162Xz2xs7@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 8b981e4d76fcb9d380ae1cbd4c9eeec1726e593e (commit)
via 69031f7674295d6d95219a97063c718beecc1052 (commit)
from 340f11ccbc855be7c8a2d46691d9ffef56aa00cc (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 8b981e4d76fcb9d380ae1cbd4c9eeec1726e593e
Merge: 340f11ccbc 69031f7674
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Apr 5 22:29:37 2024 +0200
Merge remote-tracking branch 'origin/master' into next
-----------------------------------------------------------------------
Summary of changes:
config/suricata/suricata.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/suricata/suricata.yaml b/config/suricata/suricata.yaml
index fb4f9426b..5bec5cd01 100644
--- a/config/suricata/suricata.yaml
+++ b/config/suricata/suricata.yaml
@@ -351,7 +351,7 @@ nfq:
bypass-mask: 1073741824
# route-queue: 2
# batchcount: 20
- fail-open: yes
+ fail-open: no
##
## Step 5: App Layer Protocol Configuration
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-04-05 20:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4VB98M162Xz2xs7@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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