[bt-devel] ssh update configuration change notice

[Fred Saalbach]

I updated ssh after mandrake poseted a security bug fix

cvs then started asking for passwords which broke cervisia.

The problem turns out to be a change in the /etc/ssh/ssh.config file.
This was posted to sourceforge docs about the issue:

Fred Saalbach
-----------------------------

How do I specify which SSH protocol I wish to use?
As stated previously, the SSH1 and SSH2 protocols make use of entirely different
public key cryptography systems. Since SSH1 keys will not work with the SSH2
protocol and SSH2 keys will not work with the SSH1 protocol, it is vital that
you properly configure your SSH client to make use of the protocol version that
matches the keys you intend to use. Failure to match protocol version to that
which matches your SSH keys will result in those keys being ignored. This is the
most common problem that users encounter when trying to key SSH keys working for
the first time.

It should also be noted that certain distribution and software upgrades have
changed protocol preference during the upgrade process. If your key is no longer
being used (you were using SSH keys, but are now being prompted for a password),
check to make sure the protocol preference was not changed without your
knowledge.

Protocol selection occurs in different places in different SSH client suites. If
you are making use of the OpenSSH SSH client suite, you should edit your
/etc/ssh/ssh_config file. Protocol preference is specified within this file in
lines similar to the following (the first sets a preference of SSH2 over SSH1,
the second sets a preference of SSH1 over SSH2):
Protocol 2,1
Protocol 1,2