HttpFilteringEngine
HttpFilteringEngine copied to clipboard
TechnikEmpire
Transparent filtering TLS proxy.
[172.217.12.37.sslreport.txt](https://github.com/TechnikEmpire/HttpFilteringEngine/files/1404425/172.217.12.37.sslreport.txt) [216.58.216.69.sslreport.txt](https://github.com/TechnikEmpire/HttpFilteringEngine/files/1404426/216.58.216.69.sslreport.txt) [172.217.8.5.sslreport.txt](https://github.com/TechnikEmpire/HttpFilteringEngine/files/1404427/172.217.8.5.sslreport.txt)
#131 may not be accurate in describing what the problem is. I believe this is actually the problem, but a solution as described in 131 might allow us to keep...
There are a few critical exceptions thrown for super edge case, critical errors that get caught. However, it appears that one of these has happened, and just shut down the...
We have a few critical exceptions that get thrown on the C++ side. We also have some in the C# diverter. In all these cases, lets call ReportError before throwing...
At some unknown point in history, our use `enable_shared_from_this` has ended up causing every connection to get pinned in memory forever. Massive leak, unsure how this snuck by unnoticed for...
http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/overview/core/handler_tracking.html
Because we pack the same pointers in internal storage with more than one reference (using SAN's etc for each cert), all of the contexts we store could potentially get double-free'd,...
We need a MacOS backend. This will involve building a MacOS specific in memory certificate store, as well as a MacOS specific diversion back end.
The contexts end up advertising SSL3. Nuff said. Related to #131
Didn't realize that TLS contexts were so memory hungry. After extended browsing, this will eat and hold forever a tremendous amount of RAM. This feature needs to be undone.