On Thu, 8 Jan 2009, Dan Brown wrote:

>> No. When you use a client certificate, you always also provide a private
>> key (and the associated passphrase for it). There's no escape from that.
>
> Well that is what I had thought as well. I am dealing with a third party
> which requires HTTPS with client authentication. I provided my public key,
> as well as a PKCS12 digital id generated from the private and public keys

Why don't just ask the "third party" what they require and how?

> They provided us with only public keys. I am
> guessing they have their end setup something like what is described here:
>
> http://msdn.microsoft.com/en-us/library/aa302412.aspx

That speaks of client certs, and you use clients in combination with private
keys. At least I don't know of any other way.

> Maybe I should simply be connecting and posting their public certificate
> immediately as a part of the headers?

That would be highly unusual.

-- 
  / daniel.haxx.se
_______________________________________________
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-php