Description of Problem:


Version-Release number of selected component (if applicable):


How Reproducible:

Every time

Steps to Reproduce:
1. Set your clock to this date:

date 030701012002

2. Fire up the X server point it at a configured xdm server:

X -query foo

3. Set your date forward in time many days:

date 040402562002

Actual Results:

After a few minutes the X server will start hogging the CPU and will probably
crash or exit after a while with an error:

XDM: Too many retransmissions

Expected Results:

The X server should keep running as normal.

Additional Information:
	
It appears that after looking at the code that this bit of the code has a very
low tolerance for both clock skew, because someone changed the time, and when
the integer that holds the time rolls over its value.  It's very likely that the
retransmission times for contacting the xdm server will be fully screwed up.

I've got a patch that both adds support for detecting clock skew, and correcting
 from that condition, and handles the rollover of the value correctly.