Closed Bug 15623 Opened 25 years ago Closed 24 years ago

keygen does not work

Categories

(Core :: DOM: Core & HTML, defect, P3)

All
Other
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: teruko, Assigned: warrensomebody)

References

()

Details

(Whiteboard: [nsbeta2+][dogfood-];071300:waiting for PSM 1.2 release-ckritzer;)

Attachments

(1 file)

In the above URL page, keygen field does not show anything.

Tested 10-01 Linux, 10-01 Mac, and 10-03 Win32 M10 build.
Status: NEW → ASSIGNED
Target Milestone: M12
Blocks: 16950
Summary: keygen does not work → [dogfood] keygen does not work
Marking as dogfood.
Assignee: kmcclusk → rickg
Status: ASSIGNED → NEW
Component: HTML Form Controls → Form Submission
Rick, we need to implement the logic to get the keygen contents. Talk to me for
details. After that we'll re-assign to the security guys to fill in the rest.
Assignee: rickg → kmcclusk
Kevin -- please outline your plan here, and be specific about what you need me
to do. Thanks.
Marking PDT-...unless security group is blocked for dogfood on this...lord?  If
needs to be PDT+, please remove [PDT-] with comment and we bugs will bounce back
to us.
Target Milestone: M12 → M13
Status: NEW → ASSIGNED
QA Contact update.
Target Milestone: M13 → M15
Appears to work on:
   - Linux6 2000-01-20-08 Commercial build
   - Win98 2000-01-20-08 Mozilla build
   - MacOS86 2000-01-20-08 Commercial build
Marking WORKSFORME
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
MARKING VERIFIED
Status: RESOLVED → VERIFIED
Hmm, KEYGEN can't be working. There is still basic work that needs to be done to 
get it to work. Reopening. 
Status: VERIFIED → REOPENED
Clearing WORKSFORME resolution due to reopen.
Resolution: WORKSFORME → ---
Putting dogfood in the keyword field.
Keywords: dogfood
Summary: [dogfood] keygen does not work → keygen does not work
Moving to M16
Target Milestone: M15 → M16
Moving to M17
Target Milestone: M16 → M17
nominating for nsbeta2 based on:
 - severity
 - visibility
 - major functionality broken
Keywords: nsbeta2
Still happens on:
 - MacOS9 2000-04-27-08-M16 Commercial Build
 - Linux6 2000-04-27-09-M16 Commercial Build
 - Win98 2000-04-27-09-M16 Mozilla Build
Reassigning to Harish for parser work.
Assignee: kmcclusk → harishd
Status: REOPENED → NEW
Target Milestone: M17 → M16
Adding Kevin and David to the CC list.
Status: NEW → ASSIGNED
The parser side implementation for KEYGEN is in.  Off to the security folks.

David, I'll forward Kevin's ( kmcclusk@netscape.com ).
Assignee: harishd → ddrinan
Status: ASSIGNED → NEW
I meant Kevin's mail.. :)
Putting on [nsbeta2+][dogfood-] radar.  Does not need a fix ASAP for daily work, 
but we should fix this for beta2.
Whiteboard: [PDT-] → [nsbeta2+][dogfood-]
Assigning to Javi since he is working on this.
Assignee: ddrinan → javi
Setting to M17.
Target Milestone: M16 → M17
mozilla work for this is checked in.  When PSM 1.2 comes out, Mozilla will be 
able to do KEYGEN form processing.

QA can verify when PSM 1.2 comes out.
Status: NEW → RESOLVED
Closed: 25 years ago24 years ago
Resolution: --- → FIXED
Javier, when does PSM 1.2 come out?
Whiteboard: [nsbeta2+][dogfood-] → [nsbeta2+][dogfood-]; waiting for PSM 1.2 release;
I believe preliminary builds of 1.2 are bundled with Netscape commercial builds.  
PSM 1.2 is in the home stretch and we hope to go into final QA soon.  
Okay...In that case, I'm re-opening this bug.
This bug still exists on:
MacOS9 2000-07-14-11-M17 Commercial
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [nsbeta2+][dogfood-]; waiting for PSM 1.2 release; → [nsbeta2+][dogfood-];071300:waiting for PSM 1.2 release-ckritzer;
Assignee: javi → beard
Status: REOPENED → NEW
Re-assigning to beard since he knows the state of PSM for Mac in the Commercial 
build.  Everything for this is there, it's just a matter of getting it built and 
included in the daily builds.
With today's commercial build, the keygen field shows a popup menu with 3 values 
in it:  2048 (High Grade), 1024 (Medium Grade), and 512 (Low Grade). I'd say that 
qualifies as working. I did have to tweak the installation a tiny amount, 
removing the file "PSMStubs.shlb" from the Components directory. This needs to be 
fixed in the build process. 
Status: NEW → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → WORKSFORME
Marking VERIFIED FIXED on:
- MacOS9 2000-07-18-10-M17 Commercial
- Linux6 2000-07-19-10-M17 Commercial
- Win98  2000-07-19-11-M17 Commercial

YAY!
Status: RESOLVED → VERIFIED
I'm reopening this because the way the keygen stuff was registered wasn't right 
-- initializing too aggressively -- and was hosing us as we were trying to bring 
up the chrome packaged in jar files.

I'm submitting a patch which appears to work, for what I've tried.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Keywords: nsbeta3
I checked in this fix because we need it for jar packaging which is landing 
today, but I won't close the bug until we can verify that this still works.
Reassigning to warren for tracking purposes.
Assignee: beard → warren
Status: REOPENED → NEW
Uh... I reopened it for re-verification because I changed/fixed the registration 
process. 

Now I'm closing it because I'm told it still works. Personally, I don't know 
what keygen is.
Status: NEW → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
Marking VERIFIED WORKSFORME on:
- LinuxRH62 2000-09-08-08-M18 Commercial
- Win98     2000-09-08-08-M18 Mozilla
- MacOS86   2000-09-07-04-M18 Commercial
Status: RESOLVED → VERIFIED
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: