|
Posted by S. Pidgorny on September 3, 2007, 4:54 am
If you were Registered and logged in, you could reply and use other advanced thread options
Open the Web site in browser and save the SSL certificate (File -
Properties - Certificates button - Details tab - Copy to File...). The
certificate is a signed public key that should be sufficient.
Peter Gutmann has written an excellent overview of PKI: "Everything you
Never Wanted to Know about PKI but were Forced to Find Out"
(http://www.cs.auckland.ac.nz/~pgut001/pubs/pkitutorial.pdf)
--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-
* http://sl.mvps.org * http://msmvps.com/blogs/sp *
> Hi, we have to communicate with a customer who insist of using secure
> communication.
> The communication will be done by a SOAP application developed
> in .NET, to the customers werbservice.
>
> Now the customer has sent us a public key to connect to their service,
> and they have asked us to send
> them our public key. So, I went to verisign and ordered a standard SSL
> test certificate. I did this
> by generating a CSR from IIS6. After giving this on the VeriSign site
> I got a certificate with which I
> could fininsh the pending request in IIS6.
>
> Now how I see this cert on IIS is that connecting clients can validate
> our webserver with VeriSign to see if it is trusted. But how can I
> send a public key to our customer. How do I generate this public.
> Or is it the same key I have received from VeriSign?
>
> I have tested adding this cert to a webbrowser and connect to the
> webserver, but this doen't seem to work.
>
> Just can't grasp this certificate realm, if somone could shed some
> light on this matter, please...
>
>
> Thanks in advance.
>
| 
XML site map