From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 3/3] Suricata: detect DNS events on port 853, too
Date: Thu, 07 Feb 2019 21:34:41 +0100 [thread overview]
Message-ID: <810148a0d8ba79e29be7e980d7a1eb4dc7aa89eb.camel@ipfire.org> (raw)
In-Reply-To: <35331b2c-281e-f72f-fdd9-de8bfa592717@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
Merged.
Best regards,
-Stefan
> As DNS over TLS popularity is increasing, port 853 becomes
> more interesting for an attacker as a bypass method. Enabling
> this port for DNS monitoring makes sense in order to avoid
> unusual activity (non-DNS traffic) as well as "normal" DNS
> attacks.
>
> Partially fixes #11808
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> Cc: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> config/suricata/suricata.yaml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/config/suricata/suricata.yaml
> b/config/suricata/suricata.yaml
> index d7302788c..67b9e8a7d 100644
> --- a/config/suricata/suricata.yaml
> +++ b/config/suricata/suricata.yaml
> @@ -208,11 +208,11 @@ app-layer:
> tcp:
> enabled: yes
> detection-ports:
> - dp: 53
> + dp: "[53,853]"
> udp:
> enabled: yes
> detection-ports:
> - dp: 53
> + dp: "[53,853]"
> http:
> enabled: yes
> # memcap: 64mb
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-07 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 17:47 Peter Müller
2019-02-07 20:34 ` Stefan Schantl [this message]
2019-02-08 12:51 ` Michael Tremer
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=810148a0d8ba79e29be7e980d7a1eb4dc7aa89eb.camel@ipfire.org \
--to=stefan.schantl@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