What about ssh 1.2.25?
Tina Iliff
GS-12 Systems Engineer
CMOS PMO
HQ SSG/ILTT
DSN: 596-2162 COMM: (334)416-2162
FAX: 596-5345 (334)416-5345
[EMAIL PROTECTED]
> -----Original Message-----
> From: Yukinori Shishime [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, May 25, 1999 9:27 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Y2K status of ssh 1.2.27?
>
>
> Hi,
>
> > From: [EMAIL PROTECTED]
> > Subject: Y2K status of ssh 1.2.27?
> > Date: Tue, 25 May 1999 08:14:26 -0400
>
> > Does anyone know the Y2K status of ssh 1.2.27? We are not prepared to
> > upgrade to 2.0.* because it does not have kerberos support.
>
> Refer to ``ChangeLog'' in ssh-1.2.27 package.
>
> ::
> :: Fri Jan 2 04:51:21 1998 Tero Kivinen <[EMAIL PROTECTED]>
> ::
> :: * Confirmed that ssh is Y2K compliant. The HAVE_USERSEC_H code
> in
> :: login_permitted function in sshd.c file is the only code that
> has
> :: some Y2K problems. The expiration format returned by
> getuserattr
> :: is only yymmddhhmm, and when login_permitted converts it to
> :: normalized format that assumes that if yy < 70 then it must be
> :: 20yy, otherwise assume it to be 19yy. This means that you
> cannot
> :: now have users whose account expires after year 2070.
>
> --
> Yukinori Shishime
> E-mail: [EMAIL PROTECTED]
