Closed Bug 39658 Opened 25 years ago Closed 24 years ago

branding the master password dialog for PSM

Categories

(Core Graveyard :: Security: UI, defect, P3)

1.0 Branch
x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 76736

People

(Reporter: morse, Assigned: thayes0993)

Details

(Whiteboard: [nsbeta2-][nsbeta3-])

The "enter master password" prompt dialog needs to be branded for PSM and clearly state which password is being requested. This is a break-off of bug 39653
Status: NEW → ASSIGNED
sairuh/morse - what does this currently say? What would you like it to say? Putting on [NEED INFO] radar.
Keywords: nsbeta2
Whiteboard: [NEED INFO]
selmer can better answer the question of what it should say because he was the original reporter of bug 39653. This bug was just a break-out of that bug.
QA Contact: sairuh → junruh
Putting on [NEED INFO] radar. Please tell us what it says...someone.
Assignee: thayes → morse
Status: ASSIGNED → NEW
Don't assign it to me, I was just the messenger. Reassigning to selmer to get an answer to your question. See my comment above
Assignee: morse → selmer
reassigning to johng and cc'ing verah. John we need to know how the dialog should be worded. Please put the wording in the bug and reassign to morse.
Assignee: selmer → johng
No, please don't reassign it to me. This is Terry Hayes' code so he should be the one who gets it.
Vera has been working with Cartman folks to update this text correctly. Reassigning to her to review what we have and give it a thumbs up or down.
Assignee: johng → verah
Putting on [nsbeta2-] radar. Not critical to beta2.
Whiteboard: [NEED INFO] → [nsbeta2-]
I don't actually own this wording; Sean Cotter does. Reassigning to him. Sean, can put the text of the dialog into this bug, please, and then reassign to the correct Cartman person (should be whoever can add the PSM branding to the dialog). Thanks!
Assignee: verah → cotter
The dialog currently reads as follows: Please enter the Personal Security Password for the PSM Private Keys security device. "PSM Private Keys" changes depending on name of the token ("security device") that requires the password. Currently, PSM has no way to determine any additional context for the password request (e.g., whether it's required for the master key that unlocks the Password Manager passwords or because a certificate is being used). Improving the wording depends on the extent to which PSM can be made smarter about context. Adding branding requires the PSM team to come up with an icon or other branding mechanism to be applied throughout the product.
Assignee: cotter → thayes
Status: NEW → ASSIGNED
Keywords: nsbeta2nsbeta3
Target Milestone: --- → M18
Adding nsbeta2 keyword to bugs with nsbeta2 triage value in status field so the queries don't get screwed up
Keywords: nsbeta2
Can't see how this hot potato would stop us from shipping. Marking nsbeta3-
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3-]
Component: Password Manager → Security: Crypto
nsbeta1
Keywords: nsbeta1
Target Milestone: M18 → ---
*** This bug has been marked as a duplicate of 76736 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified dupe.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.