From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] ruleset-sources: Update snort dl urls.
Date: Mon, 14 Oct 2019 11:28:47 +0100 [thread overview]
Message-ID: <D2EBC6DD-E230-4952-A45C-FAB1AE8BA099@ipfire.org> (raw)
In-Reply-To: <20191011184400.30599-1-stefan.schantl@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 11 Oct 2019, at 19:44, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
>
> 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 8ec848202..ef8d8482b 100644
> --- a/config/suricata/ruleset-sources
> +++ b/config/suricata/ruleset-sources
> @@ -1,8 +1,8 @@
> # Ruleset for registered sourcefire users.
> -registered = https://www.snort.org/rules/snortrules-snapshot-29130.tar.gz?oinkcode=<oinkcode>
> +registered = https://www.snort.org/rules/snortrules-snapshot-29150.tar.gz?oinkcode=<oinkcode>
>
> # Ruleset for registered sourcefire users with valid subscription.
> -subscripted = https://www.snort.org/rules/snortrules-snapshot-29130.tar.gz?oinkcode=<oinkcode>
> +subscripted = https://www.snort.org/rules/snortrules-snapshot-29150.tar.gz?oinkcode=<oinkcode>
>
> # Community rules from sourcefire.
> community = https://www.snort.org/rules/community
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-10-14 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 18:44 Stefan Schantl
2019-10-14 10:28 ` Michael Tremer [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-27 9:52 Stefan Schantl
2020-10-27 10:00 ` Michael Tremer
2020-10-27 11:01 ` Stefan Schantl
2019-05-26 18:11 Stefan Schantl
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=D2EBC6DD-E230-4952-A45C-FAB1AE8BA099@ipfire.org \
--to=michael.tremer@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