From owner-ssh@clinet.fi  Wed Mar 12 04:07:10 1997
Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by hutcs.cs.hut.fi (8.8.5/8.7.3) with ESMTP id EAA12164; Wed, 12 Mar 1997 04:07:09 +0200 (EET)
Received: (daemon@localhost) by hauki.clinet.fi (8.8.5/8.6.4) id DAA22584 for ssh-outgoing; Wed, 12 Mar 1997 03:57:24 +0200 (EET)
Received: from mickey.ee.pdx.edu (mickey.ee.pdx.edu [204.203.64.18]) by hauki.clinet.fi (8.8.5/8.6.4) with ESMTP id DAA22575 for <ssh@clinet.fi>; Wed, 12 Mar 1997 03:57:16 +0200 (EET)
Received: from crow.cat.pdx.edu (crow.cat.pdx.edu [204.203.67.140])
	by mickey.ee.pdx.edu (8.8.5/8.8.5) with ESMTP id RAA10973
	for <ssh@clinet.fi>; Tue, 11 Mar 1997 17:57:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by crow.cat.pdx.edu (8.8.5/8.8.5) with ESMTP id RAA08360
	for <ssh@clinet.fi>; Tue, 11 Mar 1997 17:57:27 -0800 (PST)
Message-Id: <199703120157.RAA08360@crow.cat.pdx.edu>
To: ssh@clinet.fi
Subject: 1.2.13 -> 1.2.17 issues...
Date: Tue, 11 Mar 1997 17:57:26 -0800
From: Eric Berggren (FurryLogic) <eric@ee.pdx.edu>
Sender: owner-ssh@clinet.fi
Precedence: bulk


  Being quite successful in popularizing the use of SSH at our site,
we've put off upgrading in fear of the compatibility issues we're
facing now. Trying to simultaneously upgrade all servers, agents,
and clients to the same version, we'd might as well renumber our
hosts.

  Is there any chance in mixing old/new versions of clients (ssh)
and agents (ssh-agent) ?  The old agents stored sockets in /tmp, which
is an error to the new clients (permission issues). Disabling this
condition as being treated as a fatal error, the new client merely
hangs with an old agent (and likewise for old clients with a new
agent). Is there an intermediate version between 1.2.14-1.2.16 that
could speak both protocols (at the probable expense of not being able
to forward) or some other code tweak ?
  The only other way seen as to use an exotic wrapper program (scripts
can't handle metachars) to try to ascertain what version of the agent
it being used); of course, with functionality being tied to the command
names, this also adds complexity of separating versions while ensuring
the preservation of basenames)

  Requesting everyone to log out to upgrade would push this off for
months...


  [i'm not on the list; apologies if covered before; the archive is
   rather small]

thanks,
-eric

=============================================================================
-                         Portland State University                         -
Eric Berggren                           Janaka Jayawardena
Network Manager & SysEng, SEAS          Director of Computer Services, CS/EE
eric@cat.pdx.edu                        janaka@cat.pdx.edu
                    Administrative Contact: cat@cat.pdx.edu
