Quote:
Originally Posted by couttsj
![View Post]()
It has taken a while, but I have confirmed that Windows 8.1 does indeed support RC4. But with CNG, not CAPI. Attached is a test program that tests 3 of the 8 available Ciphers (including the exchange cipher RSA) using Cryptography API: Next Generation.
I leave it up to you to decide if Microsoft disabled RC4 in CAPI on Windows 8 on purpose to push developers towards CNG.
I am still working on updating my TLS programs, but I am having an extreme amount of difficulty with some of the SSL calls.
J.A. Coutts
I leave it up to you to decide if Microsoft disabled RC4 in CAPI on Windows 8 on purpose to push developers towards CNG.
I am still working on updating my TLS programs, but I am having an extreme amount of difficulty with some of the SSL calls.
J.A. Coutts
This might be off topic, and I might get my wrist slapped, but this is a good way to shout out to a lot of you with the level of TLS/SSL talent all in one go.
It seems as though there's so much expertise here that between all of us, someone could start a vb6 native WebSocket implementation maybe built around RC6!
I know that the winhttp 5.1 solution works very well to accomplish https REST scenarios; that said, though respectfully, a full clsWebSocket implementation would
open up a lot of VB6 apps for the WebSocket API topology out there. Thereby extending and enhancing the usability of VB6! I've be searching for a while now and haven't
stumbled upon anyone doing that. There's an impressive multiprocess RPC server solution with no TLS/SSL but nothing targeting the websocket standard.
Maybe that could be enhanced to get us there. Think about it trading algo's in VB6!
My crypto experience is limited to working with Olaf's Diffie Hellman example but I've been a die hard fan and user of VB6 since Version 2. So, I will contribute what I can.
Olaf, I've got to thank you for your impressive work on vbRichClient5 and RC6 as well your overall contributions to vbClassic and the discourse. My hat is off to you! Thank you