Cert server won't issue certs. It gives a warning that the server believes the local machine system time is set to NaN. System time is correct, however.
Clayton, I think you mis-assigned this bug to me. Shouldn't the guys who own the security component get this bug?
When I run the commercial build, go to certificates.netscape.com and click on "Get Certificate", I get a page that says: <MSG> Your computer's clock is undefined minutes undefined. You will encounter problems using your certificate if your clock is set incorrectly. You must correct your clock before proceeding with enrollment. According to the server, the time is undefined. Your timezone is set to NaN hours relative to GMT. After changing your clock or timezone, restart your browser and try again. Or contact the Netscape helpdesk for assistance. </MSG> It seems that either Seamonkey or Cartman are not reporting the time properly to the server. Re-assigning to Bob Lord for further analysis.
The JS code included in certificates.netscape.com/NSEnroll.html contains references to : a. 'crypto', which is undefined. Norris thinks there's already an open bug on this not being implemented, I haven't found it yet. b. 'document.theTop', which is also undefined (this is also referred to in the original site). Seems like a bug in handling the STYLE tag.
Ahah! The crypto bug is #13794.
David can you please look at this?
Adding keyword dogfood. Mozilla cannot get certs from http://certificates because of this.
Putting on [dogfood+] radar.
This has been sitting as dogfood without a comment for a week now. What is the status? If this is not properly assigned, please bounce it to someone that can get some traction on it. Please add an expected fix date to the status whiteboard to track the motion. Thanks, Jim