From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: jul10l1r4@disroot.org
Subject: Re: [PATCH] Suricata rule: Antiphishing fix url for datasets and sids information
Date: Sun, 1 Nov 2026 12:45:54 +0100 [thread overview]
Message-ID: <d76fed7f-4bd6-428a-8472-a50380184189@ipfire.org> (raw)
In-Reply-To: <01bc914c-1126-45b0-9534-1027aa39717a@ipfire.org>
Tested-by: Adolf Belka <adolf.belka@ipfire.org>
On 31/10/2026 20:48, Adolf Belka wrote:
> Hi All,
>
> This patch is related to https://bugzilla.ipfire.org/show_bug.cgi?id=14616
>
> I reported the issue into the julioliraup github issues#13 and this patch is the proposed solution which is to have a tailored rules tarball for IPFire in the same way as for other firewalls.
>
> The commit for the creation of an IPFire specific tarball is https://github.com/julioliraup/Antiphishing/commit/c674976b3f0818db11aa9c920dd1162a136d47f6
>
> Many thanks julioliraup for the speedy response on this.
>
> Regards,
>
> Adolf.
>
> On 31/10/2026 18:59, jul10l1r4@disroot.org wrote:
>> From d5cb2a1c4156ef830e49d92679b4038739620808 Mon Sep 17 00:00:00 2001
>> From: jul10l1r4 <jul10l1r4@disroot.org>
>> Date: Sat, 31 Oct 2026 14:46:43 -0300
>> Subject: [PATCH] Suricata rule: Antiphishing fix url for datasets and sids information
>>
>> ---
>> config/suricata/ruleset-sources | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/config/suricata/ruleset-sources b/config/suricata/ruleset-sources
>> index 71d18c780..ff1289902 100644
>> --- a/config/suricata/ruleset-sources
>> +++ b/config/suricata/ruleset-sources
>> @@ -166,9 +166,10 @@ our %Providers = (
>> 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.tar.gz",
>> + dl_url => "https://raw.githubusercontent.com/julioliraup/Antiphishing/refs/heads/main/antiphishing-ipfire.tar.gz",
>> dl_type => "archive",
>> sid_range => ["6000000", "6100000"],
>> + sid_info_url => "https://julioliraup.github.io/AT/signature.html?sid=<sid>",
>> },
>>
>> ipfire_dbl => {
>
prev parent reply other threads:[~2026-11-01 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 17:59 jul10l1r4
2026-10-31 19:48 ` Adolf Belka
2026-11-01 11:45 ` Adolf Belka [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=d76fed7f-4bd6-428a-8472-a50380184189@ipfire.org \
--to=adolf.belka@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