Tuzi:
The sm_free3 CTIL can read PKCS12 (.pfx) files; most specifically from MS
Outlook. We can also build .pfx files that can be processed by MS Outlook
(they must be carefully crafted). Unfortunately, only the sm_free3 CTIL
handles this data type. It is one of the argument list inputs allowed when
creating a CTIL login for the sm_free3 CTIL.
The CML does not handle any private key material.
We have a dump utility that dump various input binaries/MIME data,
report_tool. It can decrypt/decode the .pfx file given the file (with
extension .pfx), a logins.cfg file (as in the test directory) and the
password (see the "usage" statement). The clear private key is dumped as
well as the user certificate. You can then use the certificate as input to
report_tool to be dumped (or simply change the certificate extension to .cer
and double click for MS Windows to display the certifiate). You can view
this data directly in MS Internet Explorer through the options, content tab.
Bob Colestock
VDA.
-----Original Message-----
From: tuzi@xxxxxxx [mailto:tuzi@xxxxxxx]
Sent: Thursday, June 14, 2001 3:42 AM
To: sfl maillist
Subject: How to manage a pfx / PKCS#12 file
hi,
The borwser (eg. IE) can save the certificate as pfx files. How can I get
the information such as Subject, Issuer, Validaty period, and Fingerprint
... from this pfx file. Does SFL support the usage of pfx files? I think
that this should be done by the CML(certificate management Lib), but to my
disappointment it didn't (may be I just din't find it)
Thanks all.
ps:Bob you have offered many help to me, special thanks to you.
sincerely
tuzi
tuzi@xxxxxxx