I do call the OpenSSL DH crypto API's in my openssl client. But in my Microsoft CryptoAPI client, the way they show you how to do a DH key exchange seems like it only works between two MS CryptoAPI end points. CAPI to CAPI works. OpenSSL to OpenSSL works. I just can't get OpenSSL to CAPI to work. And I believe it has something to do with the Microsoft formatting of their keys when exported. So I was wondering if anybody here has had to develop an app that needs to interoperate with a CAPI client/server.
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of karthik kumar Sent: Thursday, January 11, 2007 1:50 AM To: openssl-users@openssl.org Subject: Re: Doing a DH key exchange between OpenSSL and MS CryptoAPI if you want to use different keys then u can implement a DH key exchange calling the openSSL DH crypto APIs. Bind , i think uses the OpenSSL crypto APIs. On 12/20/06, Edward Chan <[EMAIL PROTECTED]> wrote: Has anybody done this? I can get it to work when both ends are the same. But I can't do it when they are different. I also notice the public key computed by CryptoAPI is 16 bytes larger than that computed by OpenSSL which I assume is due to some hdr information in the KEYBLOB that MS generates? Does anyone have any experience with CryptoAPI and getting it to work with OpenSSL? Thanks in advance, Ed
