Adapting proxo 4.5 to the latest OpenSSL DLLs

[JJoe]

(Nov. 02, 2014 04:10 AM)whenever Wrote:  What old problems do you mean?

1. Current browsers complain about Proxo's cert. (HalfSSL can help but in practice can cause usabilty and security problems.)
2. Original Proxomitron throws an alert for wild card certs, certs that require alternate name support, and maybe any options that it does not support.
3. Some patched Proxomitron exes do not throw alerts for certs.
4. Proxo with OpenSSL DLLs from slproweb still supports ciphers that some people believe are insufficient.

4, 3, and possibly 2 are security related, while 1 and 2 are usability problems.

This patch doesn't solve any of these problems.

ProxHTTPSProxyMII doesn't have these problems.

Edit:
I should have said 'my ProxHTTPSProxyMII doesn't have these problems.'
I changed line 54 of ProxHTTPSProxy.pyv1.1b from

Code:

sslparams = dict(cert_reqs="REQUIRED", ca_certs="cacert.pem", ssl_version="TLSv1")

to

Code:

sslparams = dict(cert_reqs="REQUIRED", ca_certs="cacert.pem")

Result is "Your SSL client is Probably Okay." at https://www.howsmyssl.com/ .
Before the change, I saw "Your SSL client is Bad." due to TLSv1 use.
I have not noticed any problems after the change.