Re: bad certificate database
Wan-Teh Chang wrote: If you would like to see this fix in NSS 3.9.1, please add a comment in Bug 53133 and we can work with John Myers to get his fix into the right NSS cvs branch. I did that, and I could also verify it as fixed in the Mozilla trunk. [...] I suspect you would need to delete the old certificate and install the certificate again with the new binaries of NSS 3.9.1 (or 3.10) that has the fix for bug 53133. This sounds bad :-(, because it seems the certs affected by this problem can't be backuped (see dependant bug 217305) ___ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
Re: bad certificate database
Jean-Marc, Jean-Marc Desperrier wrote: Wan-Teh Chang wrote: If you would like to see this fix in NSS 3.9.1, please add a comment in Bug 53133 and we can work with John Myers to get his fix into the right NSS cvs branch. I did that, and I could also verify it as fixed in the Mozilla trunk. [...] I suspect you would need to delete the old certificate and install the certificate again with the new binaries of NSS 3.9.1 (or 3.10) that has the fix for bug 53133. This sounds bad :-(, because it seems the certs affected by this problem can't be backuped (see dependant bug 217305) Here is what I would do : 1) backup your cert8.db and key3.db files 2) remove your key3.db 3) delete the cert in current Mozilla 4) upgrade to the NSS version that fixes the problem 5) restore your old key3.db 6) reimport your public cert from the CA This should preserve the private key in key3.db, and is probably the only way to do it if the key was generated in the token (not escrowed by the CA), and you were unable to back it up yourself. ___ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
bad certificate database
I have installed a certificate in Firebird 0.7, and it is corrupted because of bug 197009. I hav downloaded the new NSS 3.9 binary, but my certificate database seems to be corrupted. Even with the new binaries I still get teh bug error when trying to export my certificate. Is it possible to repair the bad database, or do I need the certificate installed again with the new binaries of NSS 3.9? (Do I need to delete the old certificate?) ___ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
Re: bad certificate database
Lars Smidt wrote on 2/14/2004, 7:29 AM: I have installed a certificate in Firebird 0.7, and it is corrupted because of bug 197009. I hav downloaded the new NSS 3.9 binary, but my certificate database seems to be corrupted. Even with the new binaries I still get teh bug error when trying to export my certificate. PSM bug 197009 is caused by NSS bug 53133. Bug 53133 was fixed after NSS 3.9 was released. If this bug fix is useful we can put it in NSS 3.9.1 and get it into Mozilla 1.7 beta. (It seems to be too late for Mozilla 1.7 alpha.) I don't track Firebird development so I don't know what NSS release Firebird is using. If you would like to see this fix in NSS 3.9.1, please add a comment in Bug 53133 and we can work with John Myers to get his fix into the right NSS cvs branch. Is it possible to repair the bad database, or do I need the certificate installed again with the new binaries of NSS 3.9? (Do I need to delete the old certificate?) My colleague Nelson or Julien can answer this question better. I suspect you would need to delete the old certificate and install the certificate again with the new binaries of NSS 3.9.1 (or 3.10) that has the fix for bug 53133. Wan-Teh ___ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
