On 07/05/2010 06:28 PM, Subrata Mazumdar wrote:
>
> I not sure about the current version (3.6) of FF, but earlier versions
> (FF 2.0 and 3.0), the key/certificate DB did not support multiple
> write interfaces i.e. DB write using one API does not get propagated
> to other API. As a result, keys/cer
On 07/05/2010 04:13 PM, james07 wrote:
> I notice the cert8.db and key3.db files get updated only when the JVM shuts
> down. That may explain why the new certificate doesn't show up. Is this
> (update of the db files) the expected behavior? It seems strange. Is there a
> way to commit the change?
>
Apologies. The connection error was due to sec_error_invalid_key. Setting the
right key usage when importing the private key fixed it.
Thanks again everyone for your help and suggestions. Truly appreciated.
James
--
View this message in context:
http://old.nabble.com/How-to-refresh-Firefox-ke
Thanks, the new database format indeed did the trick. I'm able to see the new
certificate in Certificates Manager following the import.
However I'm now getting a strange connection error when attempting to access
a test web site which requires SSL client authentication. If I unset the
environment
I not sure about the current version (3.6) of FF, but earlier versions
(FF 2.0 and 3.0), the key/certificate DB did not support multiple write
interfaces i.e. DB write using one API does not get propagated to other
API. As a result, keys/certs added by JSS API are not picked by the PSM
XPCOM
Wasn't a new version of NSS released (and thus JSS) that had a cert9.db and
key4.db? Those are SQLite3 databases, and are the only versions that actively
support multiple processes writing to them.
-Kyle H
On Mon, Jul 5, 2010 at 4:13 PM, james07 wrote:
I notice the cert8.db and key3.db fil
I notice the cert8.db and key3.db files get updated only when the JVM shuts
down. That may explain why the new certificate doesn't show up. Is this
(update of the db files) the expected behavior? It seems strange. Is there a
way to commit the change?
Also, in addition to importing the generated k
On 2010-07-01 18:10 PDT, james07 wrote:
> I'm importing the key pair into the browser's soft token.
>
> I can see that the cert8.db and key3.db files in the profile directory are
> updated and I can also see the new certificate using certutil.exe -L.
>
> However when attempting to connect to a we
I'm importing the key pair into the browser's soft token.
I can see that the cert8.db and key3.db files in the profile directory are
updated and I can also see the new certificate using certutil.exe -L.
However when attempting to connect to a website that requires client SSL
authentication in th
On 06/30/2010 10:47 PM, james07 wrote:
> Hi,
>
> I have an applet that uses JSS to import an RSA keypair into Firefox's
> keystore, as per the following code.
>
>
> CryptoManager.initialize("C:\Users\James\AppData\Roaming\Mozilla\Firefox\Profiles\y78kp7l6.default");
> CryptoMan
10 matches
Mail list logo
