Subject: Re: FUBARed by overly protective check in pkg_add.....
To: Greg A. Woods <email@example.com>
From: Andrew Brown <firstname.lastname@example.org>
Date: 04/17/1999 02:42:50
>In the case of ssh1 and ssh2 there's not much of a problem as there's
>only one really "correct" solution (i.e. ssh2 must become the default
>otherwise there's no reason for upgrading). In this case the later
>version knows how to deal with connections from, and connect to, the
>earlier version (if indeed your security is lax enough to permit either
>of those things to happen! ;-)
yes, it does...almost. i tried using them both on the same machine
(with the builtin fallback mechanism) and it works almost seemlessly.
almost. scp (from a v2 client to a v1 server) is hopelessly broken
because the ssh client steps back but does not tell scp that it has
done so, so the remote command sent is for scp version 2. which is,
of course, incompatible.
|-----< "CODE WARRIOR" >-----|
email@example.com * "ah! i see you have the internet
firstname.lastname@example.org (Andrew Brown) that goes *ping*!"
email@example.com * "information is power -- share the wealth."