Closed
Bug 124933
Opened 24 years ago
Closed 9 years ago
Success indicator should distinguish between changing builtin object token and device token password
Categories
(Core Graveyard :: Security: UI, enhancement, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: junruh, Assigned: timeless)
Details
(Whiteboard: [kerh-coz])
Attachments
(1 file)
1.) Install a hardware token.
2.) Tasks>Privacy>Password>Change Password.
3.) Change the password on the hardware token.
What happens: I get "Master Password successfully changed". This doesn't seem
correct, since I didn't really change the master password.
Comment 1•24 years ago
|
||
Technically, the password for a token is also called the master password.
Maybe a better thing to do would be to change both the change master pwd and the
success dialog to say something like:
"Change Master Password for a device"
"Master Password for the device successfully changed"
for the latter message, we can go one step further and name the device (more work).
Priority: -- → P2
Target Milestone: --- → Future
Comment 3•21 years ago
|
||
Mass change "Future" target milestone to "--" on bugs that now are assigned to
nobody. Those targets reflected the prioritization of past PSM management.
Many of these should be marked invalid or wontfix, I think.
Target Milestone: Future → ---
Updated•20 years ago
|
Whiteboard: [kerh-coz]
Updated•18 years ago
|
QA Contact: junruh → ui
Severity: normal → enhancement
Summary: Password change success dialog wording incorrect. → Success indicator should distinguish between changing builtin object token and device token password
Version: 1.0 Branch → Trunk
would someone please send me a token device :)
Comment 5•17 years ago
|
||
Bob, is this proposed change desirable from your point of view?
Comment 6•16 years ago
|
||
This bug proposes to use different wording for changing the master password.
In particular it proposes, whenever the token name is different than "Builtin Object Token", the wording shall include "your device's" in addition to "master password".
Bob, what's your opinion? Good change or unnecessary?
Comment 7•16 years ago
|
||
You mean from the software token?
I don't have a problem with adding the term 'your device's, but I would use the call PK11_IsHW() to decide to use it. The builtin softoken isn't the only possible software device (there's one that is common for mac users that gives access to the mac keyring).
bob
Comment 8•16 years ago
|
||
Actually it would be better to give the token that the password was changed for rather than a vague "master password" or "your device".
bob
Comment 9•16 years ago
|
||
Comment on attachment 329083 [details] [diff] [review]
i don't know if you can reach the failure cases, but this seems to be the general idea
r- , patch should get enhanced based on suggestions
Attachment #329083 -
Flags: review?(kaie) → review-
Comment 10•9 years ago
|
||
If this is really important to someone, I will assist them in fixing this bug, but otherwise I don't think it's worth the time to fix.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•