From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v3] download ET IDS rules via HTTPS
Date: Thu, 16 Aug 2018 19:05:56 +0100 [thread overview]
Message-ID: <4fd5a1b6d738a2d17ae77c5a3ddd276ddd244b68.camel@ipfire.org> (raw)
In-Reply-To: <1708b1ac-091c-392f-b944-918ab7efbba2@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
Merged.
On Thu, 2018-08-16 at 17:09 +0200, Peter Müller wrote:
> The Emerging Threats ruleset server supports HTTPS. It should
> be used for downloading the ruleset in IPFire, too.
>
> This also needs to be applied on the upcoming ids.cgi file for Suricata
> which I will do in a second patch.
>
> The third version of this patch superseds the first and
> second one which were broken due to bugs in the MUAs GPG
> implementation.
>
> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> ---
> html/cgi-bin/ids.cgi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/html/cgi-bin/ids.cgi b/html/cgi-bin/ids.cgi
> index 9863251e2..d9d697deb 100644
> --- a/html/cgi-bin/ids.cgi
> +++ b/html/cgi-bin/ids.cgi
> @@ -265,7 +265,7 @@ if (!$errormessage) {
> } elsif ($snortsettings{'RULES'} eq 'community') {
> $url=" https://www.snort.org/rules/community";
> } else {
> - $url="
> http://rules.emergingthreats.net/open/snort-2.9.0/emerging.rules.tar.gz";
> + $url="
> https://rules.emergingthreats.net/open/snort-2.9.0/emerging.rules.tar.gz";
> }
>
> if ($snortsettings{'ACTION'} eq $Lang::tr{'save'} &&
> $snortsettings{'ACTION2'} eq "snort" ) {
prev parent reply other threads:[~2018-08-16 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 15:09 Peter Müller
2018-08-16 18:05 ` 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=4fd5a1b6d738a2d17ae77c5a3ddd276ddd244b68.camel@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