Thanks for your report! After a bit of Googling I found a possible cause
as discussed here: http://www.networksecurityarchive.org/html/Secure-
Shell/2005-05/msg00021.html
As such, I would like to ask you to provide me with the output of the following
commands:
1. ssh -V (capital V)
2. openssl version -a
3. uname -a
4. cat /etc/issue
Also, as a workaround, you could try specifying an alternate MAC to use, like
so:
ssh -o MACs=hmac-ripemd160 <servername>
The possibilities and default order of preference according to the ssh_config
and sshd_config man pages (just look for "MACs") are:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-sha1-96,hmac-md5-96. I suggest trying
all of them and seeing if any of them work. If they do, then you could set this
option in your /etc/sshd_config on the affected SSH server machine as a
workaround.
Also according to the man pages, MAC (message authentication code) is only used
in SSH version 2 (I am not sure about this). Thus you could probably override
your ssh connections to use version 1 (can be risky) like so and avoid the MAC
problem altogether:
ssh -1 <servername>
Please respond with the information I requested (it's important in
tracking down this bug), and also please kindly inform me if any of my
suggestions have been useful. Thanks and good luck!
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Rouben
Status: Unconfirmed => Needs Info
--
ssh connections fail
https://launchpad.net/bugs/51913
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
