Return-Path: <cana@MIT.EDU>
Received: from grand-central-station.mit.edu by po11.mit.edu (8.9.2/4.7) id UAA24673; Fri, 25 Jan 2002 20:40:31 -0500 (EST)
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
	by grand-central-station.mit.edu (8.9.2/8.9.2) with ESMTP id UAA14395;
	Fri, 25 Jan 2002 20:40:15 -0500 (EST)
Received: from boeing-vertol.mit.edu (BOEING-VERTOL.MIT.EDU [18.18.2.164])
	by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id UAA10596;
	Fri, 25 Jan 2002 20:40:15 -0500 (EST)
Received: from localhost (cana@localhost) by boeing-vertol.mit.edu (8.9.3) with ESMTP
	id UAA30207; Fri, 25 Jan 2002 20:40:15 -0500
Date: Fri, 25 Jan 2002 20:40:15 -0500 (EST)
From: Cana Lynn McCoy <cana@MIT.EDU>
To: <cfyi@mit.edu>
cc: <helpstaff@mit.edu>, <sipb-staff@mit.edu>
Subject: Dialup Upgrades [ssh changes]
Message-ID: <Pine.LNX.4.30L.0201252023230.29587-100000@boeing-vertol.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Right now, the usual IAP dialup work is occurring, and there is one very
noteworthy item in the software upgrades:

We've been testing a new sshd on test.dialup.mit.edu which supports both
ssh1 and ssh2 connections.  The testing has gone well, and it is now being
deployed to all of the dialups.

This means that:

1) When the upgrades are complete, it will become possible to use ssh2 to
connect to the Athena dialup machines, which is a feature that some users
have requested.  Another notice will be sent when the upgrades are
complete, which should be by the end of next week.

2) However, even before upgrades are complete, clients may notice the
change on some dialup machines. Those who use programs that will attempt
to use ssh2, and fall back to ssh1 if they have to, may suddenly find
themselves using ssh2.  Most programs handle this gracefully.  We have had
reports, however, of programs that will alert the user that a change has
occurred.  For instance:


 Host Identifcation Warning-- One of the following may have occurred

  1. Either the administrator Host Identification could have changed.
  2. Could have changed from SSH1 to SSH2.
  3. Someone could be eavesdropping on you right now (man in the middle attack).


Messages like this should not be overlooked.  However, consultants should
be aware that #2 in that list of possibilities will be applicable to the
Athena dialups over the next few days.  Work with clients to make sure
that the switch from ssh1 to ssh2 is what has occurred.

Cana McCoy
Athena Server Operations


