Dear Maintainer,

This bug is related to #1123609

The trailing '1' on the binary 'ssh1' and the package name
'openssh-client-ssh1' confused me.

The package provides a range of legacy ciphers and protocol features,
but the naming puts all the focus on one of those, which isn't even
enabled by default, i.e.

    ssh1 user@host

opens an SSH-2 connection, though the name led me to expect an
SSH-1 connection.

It is _possible_ to use the package to open an SSH-1 connection,
by providing non-default options, but this is just one of many
common uses. Others are:

- ssh-rsa signatures
- ssh-dss
- RC4, Blowfish, DES and old DH groups
- SHA-1 based KEX/MAC

The best idea I have is to rename the binary to "ssh-legacy"
and the package to "openssh-client-legacy" to better indicate
what they are for. With time, the number of features which are
considered 'legacy' will almost certainly grow.

Renaming binaries and packages causes confusion too, and that alone
may be enough reason to drop this suggestion. I have submitted a
separate bug report suggesting a reworded package description
because that has no obvious downsides. It's bug #1123609.

*** Reporter, please consider answering these questions, where appropriate
***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***