Closed
Bug 106939
Opened 23 years ago
Closed 23 years ago
Change Master Password Dialog come up with wrong device selected when prompting for new password.
Categories
(Core Graveyard :: Security: UI, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
psm2.2
People
(Reporter: ssaux, Assigned: KaiE)
Details
Attachments
(1 file)
717 bytes,
patch
|
javi
:
review+
shaver
:
superreview+
|
Details | Diff | Splinter Review |
Change Master Password Dialog come up with wrong device selected when prompting for new password: To reproduce you must not have your Software Security Device Password set and you must have a hardware device installed. One way to do that (how I ran into this bug) is to have a hardware device installed, then blow you key and cert dbs but keep your secmod.db. I suspect that if you reset your master password you would have the same problem. Once this setup is complete follow these steps: Start the browser in a way that it will not prompt you for a software security device pwd. import a p12 file. You're prompted for the device you want to store the token into. choose the software security device. The set password dialog comes up, but the device selected is the Hardware Token (which already has a password). You must manually change the drop down to the Software Security Device. Expected: Since the reason the set password dialog comes up is that you don't have a Software Security Password, the set Master password should come up with that device selected.
Reporter | ||
Updated•23 years ago
|
Priority: -- → P1
Target Milestone: --- → 2.2
Assignee | ||
Comment 1•23 years ago
|
||
My opinion: If you have previously decided which token you want to use, the change password dialog should not allow you to select a different token. You obviously have already decided that you want to store it on the software security device. The change password dialog should only allow to change the password for this token. When I look at changepassword.xul and password.js, I think the dialog is already designed to behave that way. If it doesn't, something is broken. I see code that tests, whether the dialog has been passed a token or not. In you case, a token name should have been passed to the dialog. If it had been passed, the token selection would not have been visible. The solution to this bug is: We need to find out, why the token name does not arrive in the dialog, or maybe why the dialog behaves wrong.
Assignee | ||
Comment 2•23 years ago
|
||
I found the cause for this bug, as well as the yet unexplained error message in bug 110454. The function name is written incorrectly. I will attach a patch that corrects the problem. The dialog is now able to obtain the requested token name, and does show this name in the dialog, but does no longer show a list to select from.
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•23 years ago
|
||
Assignee | ||
Comment 4•23 years ago
|
||
Javi, can you please review?
Comment 5•23 years ago
|
||
Comment on attachment 59150 [details] [diff] [review] Suggested Fix r=javi
Attachment #59150 -
Flags: review+
Comment on attachment 59150 [details] [diff] [review] Suggested Fix That sucks; that method should be interCaps, not InterCaps. Can you fix the IDL and callers? sr=shaver on this coping mechanism, though.
Attachment #59150 -
Flags: superreview+
Assignee | ||
Comment 7•23 years ago
|
||
checked in, fixed
Status: ASSIGNED → RESOLVED
Closed: 23 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
•