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] suricata: add julioliraup/Antiphishing ruleset
Date: Wed, 8 Jul 2026 11:18:30 +0100	[thread overview]
Message-ID: <39419EE9-9788-4450-86AE-ADA640DBBF60@ipfire.org> (raw)
In-Reply-To: <6623153994b753312c6edc95dbfe4753@disroot.org>

Hello Julio,

Thank you very much for your patch.

I merged it into our next branch, but I wasn’t able to apply it directly as a lot of whitespace has been broken and lines had been wrapped. So I manually edited the file and copied your block. Please check for me that didn’t miss anything.

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

Once this release go out, would you be able to publish an announcement to your users that this ruleset is now available in IPFire?

All the best,
-Michael

> On 6 Jul 2026, at 06:13, jul10l1r4@disroot.org wrote:
> 
> From 66a41675b0cc1b793b14cc367a545e48fe83160b Mon Sep 17 00:00:00 2001
> From: jul10l1r4 <jul10l1r4@disroot.org>
> Date: Mon, 6 Jul 2026 01:45:32 -0300
> Subject: [PATCH] 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..bbd9fa3b1 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 for protect against phishing attack",
> + requires_subscription => "False",
> + dl_url => "https://raw.githubusercontent.com/julioliraup/Antiphishing/refs/heads/main/antiphishing.rules",
> + dl_type => "plain",
> + 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-08 10:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  5:13 jul10l1r4
2026-07-08 10:18 ` Michael Tremer [this message]
2026-07-12 23:11 ` [PATCH v2] " jul10l1r4
2026-07-15 13:36   ` Michael Tremer

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=39419EE9-9788-4450-86AE-ADA640DBBF60@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