Well the story is now more confusing for me. I disabled the Ciphers and
MACs fields in /etc/ssh/ssh_config and connected again. This time, I'm
able to get into my work machines without problem.
However, at the time, enabling the fields was the difference between
success and failure.
I know the V
Public bug reported:
jlquinn@wyvern:~$ lsb_release -rd
Description:Ubuntu 13.10
Release:13.10
I log into work over an AT&T vpn. When I upgraded my client to Ubuntu 13.10, I
was unable to ssh into my work machines. The ssh version upgrade was
2014-02-06 12:45:05 upgrade openssh-cl
Alternatively, I moved 3des-cbc to the front of the Ciphers list in
$HOME/.ssh/config
Will this bite me someday?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot
ssh -c 3des-cbc host
seems to work around this problem for me for now. +1 to fixing this
ASAP?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
cannot login anymore: R
