Re: Y2K and Radius: maExpireDate above 12-31-1999 (year 2000) produces login failures

Mike Stankavich ( (no email) )
Fri, 24 Jul 1998 17:00:51 -0700

What about the SQL Server default behavior of converting 2-digit years
between 00 and 49 to 2000-2049 and 50-99 to 1950-1999? That would explain
why 2050 didn't work...

Mike Stankavich, CTO

NorFab/ISP, Inc.
921 SW Washington St
Portland OR 97205

email: mike@ethergate.com
www - business: http://www.ethergate.com
www - personal: http://users.ethergate.com/mike

(503) 972-2822 direct
(503) 972-2810 office
(503) 972-2823 fax

-----Original Message-----
From: Dale E. Reed Jr. <daler@iea-software.com>
To: radiusnt@iea-software.com <radiusnt@iea-software.com>
Date: Friday, July 24, 1998 4:35 PM
Subject: Re: Y2K and Radius: maExpireDate above 12-31-1999 (year 2000)
produces login failures

Mike Miller wrote:
>
> Radius 2.2 is y2k compliant. In our testing yesterday we were using a
date
> of 1-1-2050 (randomly picked.. no special reason). I tried the test again
> today, except this time with a date of 1-1-2010. It appears RadiusNT 2.2
> will handle 2010 completely fine. I doubt RadiusNT 2.2 will ever use a
> date larger than 2010 (like 2050), unless of course by some wierd miracle
a
> customer decides to pay 50 years Internet access in advance (yeah right!).
> I am content with a successful test.

I'm guessing the issue resolves around the year 2017 (If I remember
right).
RadiusNT 2.5 should be able to handle the years higher than 2017. 2.2
(which parses the dates) may have problems with it.

--Dale E. Reed Jr.  (daler@iea-software.com)_________________________________________________________________       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQsInternet Solutions for Today  |   http://www.iea-software.com