I have to analyse SSL traffic of an executable under Windows 10. This sounds trivial really, why not just use Burp suite?
Using Burp I setup an invisible proxy listenning on port 443 and redirecting to target host's IP. Then in Windows hosts file I add the line "127.0.0.1 ex.host.com". After adding Burp CA into Windows Trusted CA store it works well when I navigate to ex.host.com with Chrome.
But the application I have to analyse doesn't seem to take into account the computer trusted CA and I have the error "unknown_ca" in burp.
The app use OpenSSL and the OpenSSL code is embed in the exe (no DLL). Meaning that I also have no way to locate through the code in a debugger for instance.
What I need is to force the application to trust my Burp CA but I need a hint to do that.
I tried using oSpy but after attaching oSpy to the target process It's stuck with the splash "Waiting for logging agent."