Closed Bug 58468 Opened 25 years ago Closed 24 years ago

Move the PSM startup initalization from xul to c.

Categories

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

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

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: dougt, Assigned: javi)

Details

Based on bug 57395, we should move the initialization of the secure browser component from the xul overlay into the nsBrowserInstance.
Actually, we should make the PSM initalization code more generic so that any "security manager" can be started up. Then we should move this initialization into the docloader or some other generic place. This needs to happen so that embedders do not have to do anything special to make https work. Not factoring out this initialization can lead to security holes in an embedders application (eg. not setting the lock icon properly). Assigning to javi.
Assignee: dougt → javi
adjusting summary.
Summary: Move the startup initalization from xul to c. → Move the PSM startup initalization from xul to c.
changing QA contact to junruh@netscape.com
QA Contact: nitinp → junruh
PSM 2.0 is now part of the mozilla and commercial builds and has fixed alot of UI and ssl bugs that were in PSM 1.X. I'm doing a mass setting of bugs to be FIXED. If you believe that I've closed a bug in error, please re-open it. Thanks.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Verified.
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.