joshuaaa wrote:
> var file =
> Components.classes[nsLocalFile].createInstance(nsILocalFile);
> file.initWithPath("path\to\cert.p12");
What path name exactly are you using, and on what platform? My guess is
that you're not really stumbling on importPKCS12File(), but on c
joshuaaa wrote:
> Now that I understand the process of how the nicknames work, I wonder
> if I'm missing a step in my code. The importPKCS12File() function for
> the XPCOM interface i'm using does not take any argument for a
> nickname. Neither do the other import certificate functions... what
> g
On Aug 1, 12:43 am, Nelson B Bolyard <[EMAIL PROTECTED]> wrote:
> joshuaaa wrote:
> > However, I have not succeeded yet in importing a p12 file. When I do a
> > CertDB.ImportPKCS12File(null, cert_file);
> > it runs fine, asks for the password, I enter the password, and then I
> > get an alert that
joshuaaa wrote:
> However, I have not succeeded yet in importing a p12 file. When I do a
> CertDB.ImportPKCS12File(null, cert_file);
> it runs fine, asks for the password, I enter the password, and then I
> get an alert that reads "Failed to restore the PKCS #12 file for
> unknown reasons".
. Th
joshuaaa wrote, On 2008-07-31 06:46:
> If I understand correctly, to import a certificate from a .p12 file,
> you first have to store the private key on the internal key storage
> token before you can import the certificate. Is this correct?
No. A PKCS#12 file contains (or should contain) both a
If I understand correctly, to import a certificate from a .p12 file,
you first have to store the private key on the internal key storage
token before you can import the certificate. Is this correct?
I've been banging my head against the wall for the past couple of days
trying to figure out why I c
6 matches
Mail list logo
