public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
* [PATCH] Suricata: detect TLS traffic on port 444, too
@ 2019-02-22 20:16 Peter Müller
  2019-02-27 15:27 ` Michael Tremer
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Müller @ 2019-02-22 20:16 UTC (permalink / raw)
  To: development

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

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-03-01 17:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-22 20:16 [PATCH] Suricata: detect TLS traffic on port 444, too Peter Müller
2019-02-27 15:27 ` Michael Tremer
2019-03-01 17:11   ` Stefan Schantl

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox