Closed
Bug 199522
Opened 21 years ago
Closed 21 years ago
Unable to access stored passwords
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: asherman, Assigned: ssaux)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030327 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030327 I used nightly 2003031208 build. Having started this build the mozilla has crashed with generating empty tallback information. This has happened, i gas, after mozilla's having tried to read stored password for a page. Any attempt (Manage Stored Passwords, for example)of this build of mozilla to read stored information (encrypted with password) lead to an alert - "Could not initialize the browser's security component" ... without asking the password Only returning to the previous build allows to read the stored information. Reproducible: Always Steps to Reproduce: 1. Install this build after using 2003031208 build with stored information 2. Run mozilla 3. Select Password Manager -> Manage Stored Passwords Actual Results: Unable to access stored informaton (passwords) Expected Results: That is wrong
Comment 1•21 years ago
|
||
-> PSM
Assignee: mstoltz → ssaux
Component: Security: General → Client Library
Product: Browser → PSM
QA Contact: carosendahl → bmartin
Version: Trunk → unspecified
Comment 2•21 years ago
|
||
This sounds like either - your certificate database became corrupted very badly If this is the case, I'm sorry that your keys for your passwords are gone, unless you have some working backup of the *.db files in your profile. - for some reason your *.db files or your profile directory is write protected I remember that I only ever saw that error message (unable to init...) when there was a read/write access problem to the files on disk.
Reporter | ||
Comment 3•21 years ago
|
||
Returning back to the old build resolves the problem and vice versa!
Reporter | ||
Comment 4•21 years ago
|
||
Addition to the previous post: so the database has renained damage-free.
Comment 5•21 years ago
|
||
One more question: Did you see the message "could not init..." only once, or do you see it all the time with some version of Mozilla?
Reporter | ||
Comment 6•21 years ago
|
||
I have seen this message many times. I have just tested one more build (2003032904) - so the bug is still present.
Comment 7•21 years ago
|
||
I think I do not understand what problem you are reporting. Is the message "could not init..." part of your problem? Do you see that message only sometimes, or do you see it always with newer builds? If I understand you correctly, you say that with new builds you are no longer able to manage your stored passwords. Question: - what is the newest build that still works? - what is the first build that is broken?
Arkady, are you still experiencing this bug in recent builds? Did you ever isolate the build in which it started? Please update the bug with recent info, or close it.
Reporter | ||
Comment 9•21 years ago
|
||
I've got no troubles scince that time. I don't remember exactly, may be I just deleted all the stored information. Thanks, that is quite well-behaved :).
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•