Closed Bug 24886 Opened 26 years ago Closed 25 years ago

[ssl] CRMF not functional

Categories

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

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

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: junruh, Assigned: javi)

References

Details

(Whiteboard: [nsbeta2+][dogfood-])

Overview Description: CRMF key generation is not functional Steps to Reproduce: 1) Visit http://warp/hardcore/cartman/crmfcgi.html 2) Click on OK for Signing Only RSA key generation. Actual Results: Nothing happens. Expected Results: CRMF Key generation should occur Build Date & Platform Bug Found: 1/21/00 Linux and WinNT Additional Builds and Platforms Tested On: Additional Information:
Changing summary.
Summary: CRMF not functional → [ssl] CRMF not functional
Blocks: 13785
setting milestone optimistically.
Target Milestone: M14
moving to m15
Target Milestone: M14 → M15
Bulk moving all Browser Security bugs to new Security: General component. The previous Security component for Browser will be deleted.
Component: Security → Security: General
needs crypto object. Over to javi.
Assignee: dougt → javi
Depends on: 13794
Accepting bug, not sure when I'll get around to fixing this though.
Status: NEW → ASSIGNED
13794 is targeted at M17, so this bug should be as well.
Target Milestone: M15 → M17
Component: Security: General → Security: Crypto
Keywords: dogfood
Is this blocking ALL key generation? PDT needs more info please.
Whiteboard: [NEED INFO]
The only way to get a cert into Mozilla without key generation being fixed is to import a *.p12 file backed up from Nova, or copy into the MozProfile Nova's cert7.db and key3.db files. That's why I'm nominating this for dogfood.
Key gen may not be working for a few weeks. Thus making [nsbeta2+] instead of [dogfood+].
Keywords: nsbeta2
Whiteboard: [NEED INFO] → [nsbeta2+][dogfood-]
Fix for this checked in. John, I'll have to give you an interim build of PSM for this to work as there is weirdness going on with the UI in Mozilla which can be worked around from the PSM side.
Forgot to mark it fixed las time around
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This works with a special build of PSM that I got from javi. I'll see him now about adding it to the next build, and will verify it hopefully on 5/6.
This bug fix will be included in PSM version 1.2, due out in two weeks or so. When the fix is actually in the builds, I will verify it.
Verified.
Status: RESOLVED → VERIFIED
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
tracking-fennec: --- → ?
status-b2g-v1.2: --- → ?
relnote-firefox: --- → ?
relnote-b2g: --- → ?
tracking-fennec: ? → ---
status-b2g-v1.2: ? → ---
relnote-firefox: ? → ---
relnote-b2g: ? → ---
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.