Closed Bug 138179 Opened 23 years ago Closed 22 years ago

Unable to access data in password manager

Categories

(SeaMonkey :: Passwords & Permissions, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 155898

People

(Reporter: KaiE, Assigned: morse)

Details

I've been using the same profile for a while. I'm using the "store passwords" feature. I had chosen to encrypt sensitive data. During the time that I have been using the profile, I have acquired new certificates. However, I still have all the certificates since the beginning. My master password preference is set to only ask me the first time it is needed. Since a couple of days, whenever I access a page where I had a password stored for, I'm prompted to enter my master password again. But entering it correctly does not help, the form does not get filled out. Instead, I'm prompted again when I try to submit the form. In addition, when I try to open the password manager by clicking the button in the prefs, nothing happens. No dialog opens, no error message shown. I tried to switch to deselect the encrypt password option, thereby going to "obscure". When I try that, I receive an error message, that converting did not succeed. I believe password manager is no longer able to decrypt its storage of password. I think I still have the required certificates. I'm sure that I still know my master password, because I'm still able to use all certificates, as I'm doing SSL client auth and secure email. I realize that there is nowhere a preference to configure, which certificate should be used for password manager data encryption. I wonder whether the fact that I have multiple certificates, and some of them are meanwhile expired, causes password manager to be unable to decrypt the data.
Terri, can you reproduce this problem?
No reply to me question in comment 1 for over two months. I'm not able to reproduce. This sounds like a duplicate of bug 132323. *** This bug has been marked as a duplicate of 132323 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
No, I think those are different.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
I was playing with this more. I don't think it is a duplicate of 132323. Because I did not find this bug earlier today, I filed new bugs. What I see is bug 155898. *** This bug has been marked as a duplicate of 155898 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.