

You can generate the certificate via openssl on the command line if you are comfortable, or use the Opnsense GUI as shown in the squid proxy ssl documentation here: You’ll need to create an SSL cert for intercepting the traffic. Make sudotest # optional unit tests requiring privileges *hint, your vesion of git may vary in the future, adjust for the current version.*Īfter this cd into the sslsplit directory and compile the source: make To begin with get git and gmake installed on your Opnsense system. First you’ll need to compile sslsplit on your Opnsense system. A few choices that they have made make this easier on their software than on pfSense, but with enough BSD chops you can likely pull it off on either platform. Its a fork of the popular pfSense project. I’m going to be using the Opnsense as the firewall/router appliance of choice. Well using Opnsense and sslsplit you can. This is often accomplished in larger enterprise environments, but what if you’d like to do it in your lab environment or home network. There is a good deal of truth to that and that has made things like metadata analysis with things like JA3 tags more necessary some others have moved to jumping in line and decrypting traffic instead as their preferred option to retain visibility in this new world. Today as more and more traffic continues to move to a encrypted world you might think that traditional NSM (Network Security Monitoring) has gone out the window.
