From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: [PATCH v2] download ET IDS rules via HTTPS
Date: Wed, 15 Aug 2018 16:54:53 +0200 [thread overview]
Message-ID: <0a56d24f-9e94-81df-b539-e263e650b8ff@link38.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
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 second version of this patch supersedes the first one,
which contained crappy line wraps due to a bug in PGP/MIME
implementation in MUA.
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" ) {
- --
2.16.4
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEvP4SiGhEYDJyrRLk2UjyD317n2gFAlt0Pr0ACgkQ2UjyD317
n2jqvA//e2RR4h363IYzcdKfsUqEkr6DN4AJu3m5d43G00u0/d/OsN5Ai+yjsEJ/
h+uzdk9mSt6ztBg/UziG4EpAH/qX6vDwY37J+rRtvqAO7X0S3lx4/g7AeZtxgpur
LqvUOle3+IPiqCBfKJtzmOPpSMLitD+5yYLfLstjEZSTFelRYoE7uty6pQMvJKqv
t+hDPA17MfSj+NSxzcewWsUqpXvgG+p/JNsN6/7b4vCKVeooqO9llw5Q6y2ICoJS
B65yjr1JZmM6/zB55PXH0VXFzJBOMkVLq3ghQweCtCPj0q7lqLziZOy2ChEWXH0E
ERucnSW/+rDSUrBQ4xtLcYx7HhtHWKXsdQC1MeVMGCzu6sc9RQG7cuqhmew0kRGE
C5JtMnMSXIVsGkNT7GTHQheK83bB/jkp13N/FZm7UAPVirPfozkAjinXnP9NpZyw
vARDXc1t2cPzz/igozopOcRShfYClFNQb7wf/9s9VSedyRrIwbcG+qEkoghBBox8
tKNE3iUFfNVIiOcmjlapfvSSf9kh3FwGsTDoj6AP9wrGUkR4YfZ/7kPTSxxYhjK7
4c9ptKBzTXeGw2zaTOoN6N8aGPCtPCPxQgkR1XlIrb79ljHGRcWnTuIvlMnUc+1W
2eg/G1NAgjlWvBnlN0/ZwcVxJHdZycKb0OakAqtFUxf56FwRkwI=
=KaVn
-----END PGP SIGNATURE-----
reply other threads:[~2018-08-15 14:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0a56d24f-9e94-81df-b539-e263e650b8ff@link38.eu \
--to=peter.mueller@link38.eu \
--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