On 09 Oct 2002, it is alleged that Victor Probo sauntered in to 
netscape.public.mozilla.mail-news and loudly proclaimed:

> Not the same as 171331.  I had that problem Early last month (see
>    "Re: Newbe:.... 9/18/02 8:02AM"
> That problem seemed to be the 'Personal Freemail RSA 2000.8.30' DN on 2 CA 
> certs with different expiration ranges. The one that expired 8/30/02 was 
> the only one accessed, since signer is identified only by DN (anr the 
> expired appears to be first in the database).
> 
> My problem is that all the Cert databases are intact, but the S/MIME GUI 
> and processes act as if they don't exist.
> 
> Victor
> 
> Brian Heinrich wrote:
>> On 08 Oct 2002, it is alleged that Victor Probo sauntered in to
>> netscape.public.mozilla.mail-news and loudly proclaimed:
>> 
>>> Folks;
>>>    I seem to have lost the UI to associate certificates with mail
>>>    accounts (2002100804). I attempted to mail a signed message, which 
>>> failed due to lack of a cert. I have had certs associated with the 
>>> account in the
>>> past. All of the Certs still appear in the Privacy->Certs->Manage
>>> display.    Now I can't find the UI to do the association. The 
>>> security entry in
>>>    the account menue is not being displayed.  Not in the Mail account 
>>> editor
>>> nor in the Provacy->Certificates->Manage.
>>>    The prefs.js have '"mail.identity.id1.signing_cert_name"' entries for
>>> the account, but somehow the UI and the MIME processing isn't finding
>>> them.
>>>
>>> Victor Probo
>> 
>> 
>> Hmm . . . seems I'm not, then, the only person to encounter something 
>> like this:  see <http://bugzilla.mozilla.org/show_bug.cgi?id=171331>.
>> 
>> /b.

Ah.  Sorry, then.  It did, however, sound similar to what I'd experienced, 
since for me the demarcation was the NSS check-in on 26 Sept:  use an 
earlier build, it's OK; use a later build, it's horked.  As in your case, 
the problem seems to be with my DB, but a slightly different problem. . . .

/b.

-- 
Mozilla end-user questions should be directed to:
  * snews://secnews.netscape.com:563/netscape.mozilla.user.general
  * snews://secnews.netscape.com:563/netscape.mozilla.user.win32
  * snews://secnews.netscape.com:563/netscape.mozilla.user.mac
  * snews://secnews.netscape.com:563/netscape.mozilla.user.unix
Note that you need to have SSL enabled and the port set to 563.

Reply via email to