Closed Bug 26085 Opened 25 years ago Closed 24 years ago

Need strong crypto to protect single signon (and form fill) usernames, pwds, data

Categories

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

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: kevinyen, Assigned: thayes0993)

References

Details

(Whiteboard: [nsbeta2+]) 

      No description provided.
For single signon to be in beta1, usernames/pwds file(s) need to have strong 
crypto, per security review and legal feedback.

thx,
kevin
Keywords: beta1
Target Milestone: M14
PDT+
Assignee: thayes → dp
Whiteboard: [PDT+]
Status: NEW → ASSIGNED
Whiteboard: [PDT+] → [PDT+] 2/15
Removing PDT+ since this aint a requirement anymore.

Reassigning to morse.
Assignee: dp → morse
Status: ASSIGNED → NEW
Whiteboard: [PDT+] 2/15
Removing PDT+ because it's targeted for Beta2.
Whiteboard: [PDT-]
Status: NEW → ASSIGNED
Target Milestone: M14 → M15
Due to delays from the security team, this is not going to make m15.  Let's try 
for m16.
Target Milestone: M15 → M16
Keywords: beta2
Keywords: nsbeta2
Depends on: 37073
Keywords: beta2
pardon the spam: beta1 is long gone...removing this keyword. will soon replace
w/nsbeta2...
Keywords: beta1
Putting on [nsbeta2+][5/16] radar.  This is a feature MUST complete work by 
05/16 or we may pull this feature for PR2.

Moving over to Security: Crypto component.
Assignee: morse → dougt
Status: ASSIGNED → NEW
Component: Single Signon → Security: Crypto
QA Contact: sairuh → junruh
Whiteboard: [PDT-] → [nsbeta2+][5/16][PDT-]
steve, who should own this bug?  You and Terry have been working on this.
Assignee: dougt → morse
Doug, funny you should ask.  I was surprised to see it suddenly got assigned to 
you.
My part of this bug has been completed -- wallet and single signon have been 
restructured to use PSM (personal security manager, aka cartman) via the SDR 
(secret decoder ring) interface.  Remaining work is all in Terry Hayes court now 
so I'm reassigning.
Assignee: morse → thayes
*** Bug 37545 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Removing [5/16][PDT-].  Yes fix for beta2.
Whiteboard: [nsbeta2+][5/16][PDT-] → [nsbeta2+]
M16 has been out for a while now, these bugs target milestones need to be 
updated.
Setting milestone to M17.
Target Milestone: M16 → M17
Seamonkey has picked up an interim PSM 1.2 build. Marking this fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Verifying this, as the feature is there, but will open individual bugs as 
necessary.
Status: RESOLVED → VERIFIED
There already are several individual bugs opened on the feature.  They are:

41024: PSM hangs/crashes when encryption is called for (thayes)
44291: Getting new-password dialog instead of change-password dialog (thayes)
44044: Security dialog comes up when changing master password (valeski)
44299: Prompt for master password after just changing master password (thayes)
44302: Hang when exiting browser after change of password (thayes)
44110: Serious confusion if user enters wrong master password (ddrinan)
44145: Modal dialogs for sdr (thayes)
45345: Password manager doesn't work when encryption is on

Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: M17 → ---
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.