PolarProxy. The new version has been updated to support features like client certificates and a PCAP-over-IP connector.
PolarProxy now supports client-authenticated TLS handshakes for outgoing connections
to support sites that require mutual TLS (mTLS) authentication.
The following example uses the PKCS#12 client certificate "client.p12" with password "pwd"
to authenticate PolarProxy when connecting to "
Thanks to Peter Lambrechtsen for the idea!
Bypassing Decryption for Specific Domains
There are situations when it isn't appropriate to decrypt the traffic passing through PolarProxy. The traffic might, for example, contain personal or confidential information. It might also not be possible to decrypt the traffic for technical reasons, such as when clients use certificate pinning or certificate transparency to validate the server certificate. We therefore recommend that such sites are put on a "bypass" list, i.e. a list of domains for which PolarProxy should let the encrypted traffic pass untouched to preserve the end-to-end encryption between the client and server.
The new "
The following command instructs PolarProxy to send a live PCAP stream with decrypted traffic to a local PCAP-over-IP listener:
PolarProxy will automatically attempt to re-establish the PCAP-over-IP connection every 10 seconds if it goes down or cannot be established for some reason.
Only Store Packets When Instructed
PolarProxy no longer writes hourly rotated pcap files with decrypted packets
to disk unless explicitly instructed to do so with
Flushing Buffered Packets to Disk
PolarProxy now periodically flushes buffered packets to disk every 60 seconds.
The flush interval can be controlled with the "
No More Out-of-Quota Issues
We have also improved the quota handling for our privileged users, who have a license key that allows them to decrypt more than 10 GB or 10 000 TLS sessions per day. You should now be able to use your full daily quota without issues!
Posted by Erik Hjelmvik on Monday, 30 November 2020 07:45:00 (UTC/GMT)