Search the Community
Showing results for tags 'TLS'.
I have XP SP3 updated under the guise of "faux POS" (not all updates applied though) Lately I find some cases - more and more often - of HTTPS sites that : - under XP, won't open in Chrome (nor IE), i.e. using Windows own crypto API - but that - - will open under Firefox - which has its own crypto stuff - even a very old version (3.5) works ! - under Seven, for compare, same sites do open even in Chrome (or, God forbid! IE). An example page there exhibiting the phenomenon : https://www.aidanwoods.com/blog/faulty-login-pages/ Is it expected with fully updated XP SP3 and/or "POS" windows ? Or have I missed a related update ? For reference I have : crypt32.dll version : 5.131.2600.6459 (xpsp_sp3_qfe.131005-0434) and rsaenh.dll : 5.1.2600.6924 (not that I'm half sure those particular dll's are the keys of the problem)...
I've read a few posts on this forums about TLS support under Windows XP and i've just stumbled upon Stunnel, which is a proxy designed to add TLS encryption functionality to existing clients and servers. I don't know if this can solve the TLS issue under XP, but here you go to learn more about Stunnel. And here is the latest version (5.49) for Windows XP (32 bits).