public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Suricata: detect TLS traffic on port 444, too
Date: Wed, 27 Feb 2019 15:27:16 +0000	[thread overview]
Message-ID: <D8F4B6FB-F394-4E24-80F1-BBD0226BE06B@ipfire.org> (raw)
In-Reply-To: <407990e1-b28c-546a-d1b5-d99901eaee8e@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 22 Feb 2019, at 20:16, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> This is the default port for IPFire's administrative web interface
> and should be monitored by Suricata, too.
> 
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> c: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> config/suricata/suricata.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/config/suricata/suricata.yaml b/config/suricata/suricata.yaml
> index 4fbd32b85..0ff06f4ae 100644
> --- a/config/suricata/suricata.yaml
> +++ b/config/suricata/suricata.yaml
> @@ -140,7 +140,7 @@ app-layer:
>     tls:
>       enabled: yes
>       detection-ports:
> -        dp: "[443,465,993,995]"
> +        dp: "[443,444,465,993,995]"
> 
>       # Completely stop processing TLS/SSL session after the handshake
>       # completed. If bypass is enabled this will also trigger flow
> -- 
> 2.16.4


  reply	other threads:[~2019-02-27 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 20:16 Peter Müller
2019-02-27 15:27 ` Michael Tremer [this message]
2019-03-01 17: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=D8F4B6FB-F394-4E24-80F1-BBD0226BE06B@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