Re: PKCS12 Certificates and Private Keys

2008-08-01 Thread Kaspar Brand
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

Re: PKCS12 Certificates and Private Keys

2008-08-01 Thread Nelson B Bolyard
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

Re: enabling crypto hardware for NSS

2008-08-01 Thread Nelson B Bolyard
David Sadler wrote: > We have made some progress but still having problems. > > This is what we have tried ... on SLES 10 SP1 , Suse Linux, IBM zSeries > hardware. > > on the NSS side we created a certificate DB with certutil > then added openCrypto to the DB with NSS modutil > # modutil -dbd

Re: PKCS12 Certificates and Private Keys

2008-08-01 Thread joshuaaa
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

Re: enabling crypto hardware for NSS

2008-08-01 Thread David Sadler
We have made some progress but still having problems. This is what we have tried ... on SLES 10 SP1 , Suse Linux, IBM zSeries hardware. on the NSS side we created a certificate DB with certutil then added openCrypto to the DB with NSS modutil modutil -dbdir /etc/apache2/