Re: Certificates format

Miller, Timothy J. wrote:
> 
> 
> FWIW, PKCS#15 is not particularly common for software token key storage.
> For good or ill, PKCS#12 is more common, though splitting pairs into
> separate PKCS#8 and PKCS#7 structures for private and public key storage
> respectively is also used.  Peter has definite opinions about PKCS#12.  :)
>  
> 
> However, you're generally free to store keys outside a crypto module
> however you like, though it's probably a good idea to keep the private key
> wrapped up.
> 
> 
> 

 Thanks for your reply, i learn a lot of things :). On that part, it remains
two questions :

- If i store private and public key in two separated structures, how the
server part could "know" the public key if i just do :

status = cryptSetAttribute( cryptSession, CRYPT_SESSINFO_PRIVATEKEY,
privateKey );

Should I save my private key in one file, my certificate in another file
(containing public key), and before activating session importing the
certificate and add it to attribute ?

- I have no access to crypto module in my current environment so :

status = cryptAddPrivateKey( cryptKeyset, cryptContext, "My password" );

Is this enough to secure my private key when i store it ? (admitting a real
strong password). And if i do that, must i separate my keys ?

I'm sorry if answers seem obvious, i'm discovering cryptlib, I know some
things on cryptography but essentially theorical.
-- 
View this message in context: http://old.nabble.com/Certificates-format-tp34940748p34944959.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.