[25214] in Kerberos
RE: Year 2142 problem...
daemon@ATHENA.MIT.EDU (Amir Saad)
Thu Jan 5 02:30:53 2006
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 5 Jan 2006 09:29:29 +0200
Message-ID: <6C9EEE1F2D393F4396881A4981A5032548B8A3@SEXGW3K-H2020.local.bibalex.dom>
From: "Amir Saad" <Amir.Saad@bibalex.org>
To: =?iso-8859-1?Q?=22Martin_v=2E_L=F6wis=22?= <martin@v.loewis.de>
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="iso-8859-1"
Errors-To: kerberos-bounces@mit.edu
Content-Transfer-Encoding: 8bit
please give me more details about year 2038 problem,
thanks
Amir Saad
Software Engineer
________________________________
From: kerberos-bounces@mit.edu on behalf of "Martin v. Löwis"
Sent: Thu 1/5/2006 2:47 AM
To: kerberos@mit.edu
Subject: Re: Year 2142 problem...
David A. Resler wrote:
> Over the past couple of weeks we have been seeing a handful of users not
> be able to get a Kerberos ticket because the date on their computer has
> been set to the year 2142.
>
> Once the date is corrected, they can get tickets without any further
> problems.
>
> So far we have been unable to find anything in common between these
> machines. We have searched for viruses and not found any.
>
> Anyone have any ideas???
I guess Kerberos suffers from the year 2038 problem.
Regards,
Martin
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
