I have now several other questions:
- does PKCS#12 files always have the ".p12" extension in their filename?
- If no, how can I know (programatically) if they are in X.509 or PKCS#12 format?
- When using d2i_PKCS12_fp(FILE *fp, PKCS12 **p12), how can I free the p12 object?

thanks again for your time and answers :)

regards
Alexis

Alexis Lefort a écrit :
I want to do it progammatically, thanks a lot for help :)

regards
Alexis

Brad Hards a écrit :
On Saturday 28 October 2006 01:58, Alexis Lefort wrote:
  
I can't find much information about parsing a PKSC12 file, or testing
the content of a file to know if it is PEM or PKCS12.
    
Do you want to do this programmatically, or from the command line.

  
Where could I find that please?
    
man pkcs12 will provide the command line tool options

the man pages for 
* PKCS12_create
* PKCS12_parse
will provide details on how to do it programmatically. 

These documents are also available on-line. For example, see:
http://www.openssl.org/docs/crypto/PKCS12_parse.html

http://www.drh-consultancy.demon.co.uk/pkcs12faq.html may also help.

Brad
  


Ce message et toutes les pièces jointes sont confidentiels et établis a l'intention exclusive de ses destinataires. Toute modification, édition, utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. CXR Anderson Jacobson décline toute responsabilité au titre de ce message s'il a été altéré, déformé, falsifié, édité ou diffusé sans autorisation. This message and any attachments are confidential and intended solely for the addressees. Any unauthorised alteration, printing, use or dissemination is prohibited. E-mails are susceptible to alteration. CXR Anderson Jacobson shall not be liable for the message if altered, changed, falsified, printed or disseminated without authorisation.
______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]

Reply via email to