public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] ids: Fixed typo in ruleset-sources
Date: Sat, 12 Mar 2022 14:27:58 +0100	[thread overview]
Message-ID: <20220312132758.2099-1-matthias.fischer@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
---
 config/suricata/ruleset-sources | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config/suricata/ruleset-sources b/config/suricata/ruleset-sources
index 58ab91aab..1d2c6e98b 100644
--- a/config/suricata/ruleset-sources
+++ b/config/suricata/ruleset-sources
@@ -78,7 +78,7 @@ our %Providers = (
 	},
 
 	# Etnetera Aggressive Blacklist.
-	etnetera_aggresive => {
+	etnetera_aggressive => {
 		summary => "Etnetera Aggressive Blacklist Rules",
 		website => "https://security.etnetera.cz/",
 		tr_string => "etnetera aggressive blacklist rules",
-- 
2.25.1


             reply	other threads:[~2022-03-12 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-12 13:27 Matthias Fischer [this message]
2022-03-19 22:01 ` 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=20220312132758.2099-1-matthias.fischer@ipfire.org \
    --to=matthias.fischer@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