You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Suricata won't do anything to SSL encrypted traffic, but most of traffics to outside of the world or selfhosted services are encrypted. I want Suricata be able to do SSL DPI in the next release.
Describe the solution you like
Allow Suricata do SSL DPI with and without user's own CA for inbound and outbound traffic.
The text was updated successfully, but these errors were encountered:
I would suggest to integrate a open source layer-4 proxy that support SSL termination to decrypt traffic and pass it to Suricata, like what we are doing to Squid+Clamd.
Maybe we can use it to replace Squid!
Happy new year!
On January 1, 2025 9:47:37 AM UTC, Ad Schellevis ***@***.***> wrote:
For Suricata development best try their issue tracker....
Happy new year by the way.
--
Reply to this email directly or view it on GitHub:
#8173 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
Suricata won't do anything to SSL encrypted traffic, but most of traffics to outside of the world or selfhosted services are encrypted. I want Suricata be able to do SSL DPI in the next release.
Describe the solution you like
Allow Suricata do SSL DPI with and without user's own CA for inbound and outbound traffic.
The text was updated successfully, but these errors were encountered: