Re: How to use certificates?

From: Tareq Muhammad (TareqMuhammad_at_discussions.microsoft.com)
Date: 12/09/04 

Date: Thu, 9 Dec 2004 00:15:02 -0800

anther question, should server knows the client public key?
I expect that server will know the client public key, server will use it to
send a response to the client ? right ?

"Hervey Wilson [MSFT]" wrote:

> znmaster wrote:
> > Certificates are often used to encrypt or sign soap messages in WSE2. I cant
> > understand the usage of certificates in WSE2 samples. The WSE2 sdk provides
> > three certificates: Client Private.pfx, Server Private.pfx and Server
> > Public.cer. Server Public.cer doesn't have a private key. I dont know in
> > which situations they are used and their differences. What kind of
> > certificates dont have private keys?
>
> Client Private is a file that contains both a certificate and the
> private key for that certificate. It is for use by the client and is
> typically imported into the CurrentUser\Personal certificate store.
>
> Server Private is a file that contains both a certificate and the
> private key for that certificate. It is for use by the server and is
> typically imported into the LocalMachine\Personal certificate store.
>
> Server Public is a file that contains *only* the servers certificate, no
> private key. This is used by the client to encrypt messages to the server.
>
>
> > When A sends a message to B, A signs the message with his own private
> > key,and encrypts it with B's public key. When B receives the message, B
> > should verify the signature with A's public key and decrypts the message
> > with his own private key. In such situation, what kinds of certificates
> > should be used? And how can they get the key from the certificate?
>
> See above. Certificates themselves do *not* contain private key
> information, only public key information. This is why it is safe to
> share your certificate with someone else. Private keys for certificates
> are stored separately and Windows maintains a relationship between each
> certificate and it's private key (if you have the private key installed).
>
>
> --
> This posting is provided "AS IS", with no warranties, and confers no rights.
>

Relevant Pages

  • Re: Need for encryption in WSE 3.0 if using SS-avoid man-in-middle
    ... SSL only validates you are talking to a SSL certified server; ... They can simply edit the URL the client program ... can be done by using a X.509 certificate on both ends, ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: LDP client authentication fails
    ... I got the LDP working with LDAP server under server client authentication ... I did not installed the certificate in pfx format .. ... Client cert auth won't work without that. ...
    (microsoft.public.windows.server.active_directory)
  • Re: SSL & Man In the Middle Attack
    ... >> it possible for the middle man to intercept all messages from server to me ... > server sends client a signed message along with a digital certificate. ... > client generates a random secret key, ...
    (comp.security.misc)
  • Re: activesync issue
    ... On the SBS 2003 Server open the Server Management console. ... On the "Web Server Certificate" page, choose to create a new Web server ... Install the new certificate which created in above step on mobile device: ... Access to browse the Exchange Server 2003 client after you install ...
    (microsoft.public.windows.server.sbs)
  • problems encrypting Soap message using X.509 cert generated from makecert
    ... I have tried using both the sample certificate supplied with WSE 2.0 as ... I install the private key on the client and the public certificate on ... the private key on the server. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)