That's exactly what I want to do, I have a session in the config file
for the ssh1 package.
The ssh2 package breaks when it sees it.
Now what I would think as a nice polite feature would be for the
application that has the '/usr/bin/ssh' name to call the right version
of ssh if it sees a 'bad' "protocol", "Cipher" or "Ciphers" line in an
active part of the .config file.
A poorer implementation would error if it's actually told to attempt
an ssh1 connection.
Throwing it's toys out of the pram when it's supposed to be ignoring a
"Protocol 1" line is not what I would expect.
--
Rob. (Robert de Bath <robert$ @ debath.co.uk>)
<http://www.debath.co.uk/>
On Mon, 28 Nov 2016, Russ Allbery wrote:
Robert de Bath <robert$@debath.co.uk> writes:
Package: ssh
Version: 1:7.3p1-3
This error occurs whatever I attempt to connect to, even though the
particular stanza of the config as nothing to do with the host I'm
connecting to. It is obviously inefficient and much too aggressive.
I obviously still have a use for v1 as there isn't an ssh v2 sufficiently
portable to install on the machine in question.
Per /usr/share/doc/openssh-client/NEWS.Debian.gz (which apt-listchanges
would show to you automatically):
openssh (1:7.1p1-2) unstable; urgency=medium
OpenSSH 7.0 disables several pieces of weak, legacy, and/or unsafe
cryptography.
* Support for the legacy SSH version 1 protocol is disabled by default at
compile time. Note that this also means that the Cipher keyword in
ssh_config(5) is effectively no longer usable; use Ciphers instead for
protocol 2. The openssh-client-ssh1 package includes "ssh1", "scp1",
and "ssh-keygen1" binaries which you can use if you have no alternative
way to connect to an outdated SSH1-only server; please contact the
server administrator or system vendor in such cases and ask them to
upgrade.
[...]
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
