Adapting proxo 4.5 to the latest OpenSSL DLLs

[JJoe]

(Oct. 15, 2014 05:47 AM)mas Wrote:  Yes, so far so good

Interesting. It's been years since I gave up on this. IIRC...
The Proxomitron checks cert name matching. Unfortunately, Proxo doesn't understand wild card certs or SubjectAltName ( http://en.wikipedia.org/wiki/SubjectAltName ).
How did you handle this?

The last known "usable" DLL was patched to make it compatible.
Are you using an unaltered OpenSSL version 1.0.1.9 DLL?
Where did you find it?

(Oct. 15, 2014 05:47 AM)mas Wrote:  I know this app, what's with it?

I used it to monitor the Proxomitron while handled https. Dependency Walker showed unanswered requests to OpenSSL, errors, etc.

A working DLL would have been tested by verifying encryption and correct behavior but it never got that far. Even if, a "Use at own risk" warning would have been necessary.

Encryption might be verified by
https://cc.dcsec.uni-hannover.de/
https://www.fortify.net/sslcheck.html
or a network sniffer.
You could use known attacks and incorrectly configured servers to test behavior.

http://stackoverflow.com/questions/17279...certificat

Edit: I'll be moving these posts to their own thread.