You should be able to work around this by reading an encrypted message to yourself. It's OK to have the cert stored in more than one token, you just can't have the cert and key stored in the same token. The bugs related to having the cert in the cert db and in the smart card at the same time should be fixed now.
bob Yves Bronoel wrote: > I built these files from the current version on the cvs and > the bug disappeared. But there is new problem with this correction. > As there is only one source of certificates for encryption, it is > impossible to send an encrypted mail to myself. Indeed Mozilla > didn't store the certificate in cert7.db (to prevent from masking > my certificate) and it is not able to find an encryption certificate > for my address. I think this bug is already known (#114893).Will it > be fixed soon ? > > Yves Bronoel > > Robert Relyea wrote: > >> Mozilla 1.0 went out with a number of bugs in NSS. This is one of >> them. You can replace your nss3.dll ssl3.dll smime3.dll and >> softoken3.dll with more recent builds and that should solve this problem. >> >> bob >> >> Yves Bronoel wrote: >> >>> I have some problems with the certificate store of >>> Mozilla and I am wondering if it a known bug or not. >>> >>> I am writing a small PKCS #11 module and using it with >>> mozilla 1.0. In the module I have got a certificate and >>> a private key issued by OpenSSL for signing and >>> encrypting mails. The certificate is well displayed and >>> I can choose it as my user certificate and sign mails. >>> >>> But once I have read a mail signed with my own certificate, >>> and restarted Mozilla, I am not able to view my certificate in >>> "Your Certificates". It is only present in "Other People's". >>> After, I am still able to sign and decrypt mail but I can't >>> choose my certificate in "Mail & Newsgroup Account >>> Settings". The result is empty as "Your certificate" of course. >>> >>> It seems that the certificate stored in cert7.db and displayed >>> in "Other People's" is masking my own certificate. >>> >>> Another instance of this problem (without any PKCS #11 >>> module) may be seen by importing a user certificate thanks >>> to PKCS#12 when the certificate is already present in >>> "Other People's". It is said to be sucessful by Mozilla but >>> you have no access to your certificate after. Moreover, >>> after a new start of Mozilla, there is no certificate any >>> more even in "Other People's" >>> >>> I have tried my module with Netscape 4.77 and it doesn't have >>> this kind of problem. >>> >>> Yves Bronoel >>> >> > >
