From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] ruleset-sources: Update download URL for Talos rulesets.
Date: Thu, 23 Jun 2022 17:49:17 +0000 [thread overview]
Message-ID: <79f65a46-d921-db2f-26ea-baae28795348@ipfire.org> (raw)
In-Reply-To: <e7978703eea89c6608f2e9e71f3ddefb9447d9dc.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2690 bytes --]
Hello Stefan,
thanks for your reply.
Michael already explained the nature of this patch to me, and it is included
wit C169: https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=b77b41a579982fd6ee524f1c8ee45fea03bb9b76
Thanks for your follow-up and elaboration though. :-)
All the best,
Peter Müller
> Hello Peter,
>
> if possible it would we great to ship this with core 169. It is simply
> a minor change and allows those who are using the rulesets from Talos
> to get the latest rules again.
>
> Best regards,
>
> -Stefan
>> Hello Stefan,
>>
>> thank you for submitting this.
>>
>> Does this patch urgently need to go into Core Update 169? While there
>> is still an
>> issue left to solve with the update, I would rather abstain from
>> packing any patch
>> that now comes up into it as well...
>>
>> Apart from that:
>>
>> Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
>>
>> Thanks, and best regards,
>> Peter Müller
>>
>>
>>> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
>>> ---
>>> config/suricata/ruleset-sources | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/config/suricata/ruleset-sources
>>> b/config/suricata/ruleset-sources
>>> index 1d2c6e98b..592cbedf0 100644
>>> --- a/config/suricata/ruleset-sources
>>> +++ b/config/suricata/ruleset-sources
>>> @@ -23,7 +23,7 @@ our %Providers = (
>>> website => "https://www.snort.org",
>>> tr_string => "registered user rules",
>>> requires_subscription => "True",
>>> - dl_url =>
>>> "https://www.snort.org/rules/snortrules-snapshot-29190.tar.gz?oinkcode=
>>> <subscription_code>",
>>> + dl_url =>
>>> "https://www.snort.org/rules/snortrules-snapshot-29200.tar.gz?oinkcode=
>>> <subscription_code>",
>>> dl_type => "archive",
>>> },
>>>
>>> @@ -33,7 +33,7 @@ our %Providers = (
>>> website => "https://www.snort.org",
>>> tr_string => "subscripted user rules",
>>> requires_subscription => "True",
>>> - dl_url =>
>>> "https://www.snort.org/rules/snortrules-snapshot-29190.tar.gz?oinkcode=
>>> <subscription_code>",
>>> + dl_url =>
>>> "https://www.snort.org/rules/snortrules-snapshot-29200.tar.gz?oinkcode=
>>> <subscription_code>",
>>> dl_type => "archive",
>>> },
>>>
>
prev parent reply other threads:[~2022-06-23 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 6:03 Stefan Schantl
2022-06-23 10:30 ` Peter Müller
2022-06-23 11:31 ` Michael Tremer
2022-06-23 17:07 ` Stefan Schantl
2022-06-23 17:49 ` Peter Müller [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=79f65a46-d921-db2f-26ea-baae28795348@ipfire.org \
--to=peter.mueller@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