You have been subscribed to a public bug:

Hi,

I do not know, what happened today, but some upgrades seem to have
broken my ssh client. I can not use ssh to login to my remote server
from jaunty client to jaunty server. Both sides are up-to-date.

croess...@desktop ~/.ssh $ cat config 
#
# Default settings
#
Host *
    Compression yes
    ForwardAgent yes
    ForwardX11Trusted yes
    ServerAliveInterval 30
    Ciphers aes256-cbc
    MACs hmac-sha1
    ControlMaster auto
    ControlPath /home/croessner/.ssh/%h:%p

ssh -v roessner1.roessner-net.de 
OpenSSH_5.1p1 Debian-5ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /home/croessner/.ssh/config
debug1: Applying options for *
debug1: Applying options for roessner1.roessner-net.de
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: auto-mux: Trying existing master
debug1: Control socket "/home/croessner/.ssh/roessner1.roessner-net.de:216" 
does not exist
debug1: Connecting to roessner1.roessner-net.de [85.10.196.195] port 216.
debug1: Connection established.
debug1: identity file /home/croessner/.ssh/identity type -1
debug1: identity file /home/croessner/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/croessner/.ssh/id_dsa type 2
debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.DSA-2048
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 
Debian-5ubuntu1
debug1: match: OpenSSH_5.1p1 Debian-5ubuntu1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-5ubuntu1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes256-cbc hmac-sha1 z...@openssh.com
debug1: kex: client->server aes256-cbc hmac-sha1 z...@openssh.com
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<4096<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '[roessner1.roessner-net.de]:216' is known and matches the RSA 
host key.
debug1: Found key in /home/croessner/.ssh/known_hosts:462
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
buffer_get_ret: trying to get more bytes 4 than in buffer 0
buffer_get_int: buffer error

I also have a intrepid laptop. From there I still can login, so it is
not a problem on the server.

I tried to kill seahorse-* and ssh-agent, but this does not solve the
problem. This is critical for me.

** Affects: seahorse (Ubuntu)
     Importance: Undecided
         Status: New

-- 
[jaunty] can not login using ssh anymore
https://bugs.launchpad.net/bugs/328277
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to seahorse in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to