public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: jul10l1r4@disroot.org
Cc: development@lists.ipfire.org
Subject: Re: [PATCH v2] suricata: add julioliraup/Antiphishing ruleset
Date: Wed, 15 Jul 2026 14:36:03 +0100	[thread overview]
Message-ID: <00ABBFC0-CF27-4151-A86F-3D029E324309@ipfire.org> (raw)
In-Reply-To: <f6cb16d250ce1b1a35be3d6056a1d4a6@disroot.org>

Hello Julio,

Thanks for the patch. As you can see, this was mangled as well, but I made the changes manually. Please let me know if this is all correct:

https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=b96061d75d4c7bc1950f6732af4b9c8863eaadb6

All the best,
-Michael

> On 13 Jul 2026, at 00:11, jul10l1r4@disroot.org wrote:
> 
> From 3fa7a324453227d2329ce068ca7e9bdfe386d4ff Mon Sep 17 00:00:00 2001 From: jul10l1r4 <jul10l1r4@disroot.org> Date: Mon, 6 Jul 2026 01:45:32 -0300 Subject: [PATCH v2] suricata: add julioliraup/Antiphishing ruleset This patch adds the 'julioliraup/antiphishing' ruleset to the Suricata configuration. This feed is hosted on GitHub and focuses on blocking phishing threats at the network layer. It is already officially indexed by suricata-update and frequently updated. --- config/suricata/ruleset-sources | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/config/suricata/ruleset-sources b/config/suricata/ruleset-sources index 5b9073d85..f7ae8b026 100644 --- a/config/suricata/ruleset-sources +++ b/config/suricata/ruleset-sources @@ -160,6 +160,17 @@ our %Providers = ( sid_range => ["2610000", "2619999"], }, + # julioliraup/Antiphishing protect against phishing attack + julioliraup_antiphishing => { + summary => "julioliraup/Antiphishing", + website => "https://github.com/julioliraup/Antiphishing", + tr_string => "julioliraup/Antiphishing to protect against phishing attack", + requires_subscription => "False", + dl_url => "https://raw.githubusercontent.com/julioliraup/Antiphishing/refs/heads/main/antiphishing.tar.gz", + dl_type => "archive", + sid_range => ["6000000", "6100000"], + }, + ipfire_dbl => { summary => "IPFire DBL - Domain Blocklist", website => "https://www.ipfire.org/dbl/", -- 2.39.5



      reply	other threads:[~2026-07-15 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  5:13 [PATCH] " jul10l1r4
2026-07-08 10:18 ` Michael Tremer
2026-07-12 23:11 ` [PATCH v2] " jul10l1r4
2026-07-15 13:36   ` 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=00ABBFC0-CF27-4151-A86F-3D029E324309@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=jul10l1r4@disroot.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