23028 - Cert server doesn't get correct machine time from Seamonkey

Status: VERIFIED DUPLICATE of bug 28333

(Core Graveyard :: Embedding: APIs, defect, P3)

Description

[clayton]

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.

Comment 1

[Nisheeth Ranjan]

Clayton, I think you mis-assigned this bug to me.  Shouldn't the guys
who own the security component get this bug?

Comment 2

[Nisheeth Ranjan]

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.

Comment 3

[Bob Lord]

That site has some javascript which compares the GMT time on the client to that 
of the server.  Since many cert deployment problems are really local workstation 
clock skew errors, IS decided to stop you in your tracks if you're more than a 
few minutes off.

I haven not looked closely at the script, but it seems likely that there's 
something wrong with Javascript or the way the Javascript works on that page.

Clayton, can I toss it back in your area to have someone work on it?  The 
contact in IS who maintains this is Bill Burns.  I'll let him know this is 
coming his way.

Comment 4

[rogerl (gone)]

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.

Comment 5

[rogerl (gone)]

Ahah! The crypto bug is #13794.

Comment 6

[Bob Lord]

David can you please look at this?

Comment 7

[John Unruh]

Adding keyword dogfood. Mozilla cannot get certs from http://certificates 
because of this.

Comment 8

[leger]

Putting on [dogfood+] radar.

Comment 9

[Jim Roskind]

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

Comment 10

[David P. Drinan]

This bug is a dup of 28333.

The problem is not in the security code but the Date object in JavaScript.

*** This bug has been marked as a duplicate of 28333 ***

Comment 11

[John Unruh]

Verified duplicate.