Closed Bug 279565 Opened 20 years ago Closed 19 years ago

Crash after certificate installation with SSD master password set

Categories

(Core Graveyard :: Security: UI, defect)

Other Branch
x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: init, Assigned: KaiE)

Details

(Keywords: crash, stackwanted)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0

I use the (swedish) banking service at 

http://www.skandiabanken.se/

At first use, they install a new root certificate and a personal certificate
that belongs to me. I did this a few days ago, and it worked perfectly. I then
remembered that in my old Mozilla (in Fedora Core 1), the certificates were
protected by encryption with the Software Security Device (SSD). I decided to
set up a master password to enable this additional protection. This required a
reinstallation of the certificates.

When I proceeded to install the certificates, everything worked just like the
last time, except that when I completed the last step (the actual certificate
installation), Firefox unexpectedly quits. It seems to have completed the
certificate download and installation though, since when I restarted the browser
the certificates are installed and the banking service works as intended.


Reproducible: Couldn't Reproduce
Group: security
Keywords: crash
please install talkback, create a new profile, crash again and report the
talkback incident id.
Assignee: bugs → kaie
Component: Preferences → Client Library
Keywords: stackwanted
Product: Firefox → PSM
QA Contact: mconnor
Product: PSM → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.