Re: Certificates format

Peter Gutmann wrote:
> 
> A PKCS #15 file is a private-key file.  To exchange the certificate with
> someone else, just export it using cryptExportCert() in whatever format
> you
> like (CRYPT_CERTFORMAT_CERTIFICATE or CRYPT_CERTFORMAT_CERTCHAIN, or
> CRYPT_CERTFORMAT_TEXT_CERTIFICATE or CRYPT_CERTFORMAT_TEXT_CERTCHAIN if
> you
> want them in base64-encoded text format) and the other side will be able
> to
> read it.
> 

I come back on that topic to be really sure i have correctly understood the
process.

Server side :
- key creation (RSA priv/pub)
- certificate creation (XYZZY mode for now)
- open a keyset to store my private key (a PKCS #15 file). I add private key
and certificate.
- starting a session and setup it with my private key.

Client side :
- Once session is established, i can use cryptExportCert() to save the
certificate, and later use cryptImportCert() to check it again.

I should not use cryptExportCert() on server side, because i cannot add
resulting file in my session to transmit it to client, is that right ?
-- 
View this message in context: http://old.nabble.com/Certificates-format-tp34940748p34957515.html
Sent from the Cryptlib mailing list archive at Nabble.com.


_______________________________________________
Cryptlib mailing list
[email protected] via Mail: [email protected]
Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/
http://news.gmane.org/gmane.comp.encryption.cryptlib
Posts from non-subscribed addresses are blocked to prevent spam, please
subscribe in order to post messages.