can not login using ssh anymore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Keyring |
Unknown
|
High
|
|||
gnome-keyring (Fedora) |
Fix Released
|
Medium
|
|||
gnome-keyring (Ubuntu) |
Fix Released
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
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.
croessner@desktop ~/.ssh $ cat config
#
# Default settings
#
Host *
Compression yes
ForwardAgent yes
ForwardX11T
ServerAlive
Ciphers aes256-cbc
MACs hmac-sha1
ControlMaster auto
ControlPath /home/croessner
ssh -v roessner1.
OpenSSH_5.1p1 Debian-5ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /home/croessner
debug1: Applying options for *
debug1: Applying options for roessner1.
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: auto-mux: Trying existing master
debug1: Control socket "/home/
debug1: Connecting to roessner1.
debug1: Connection established.
debug1: identity file /home/croessner
debug1: identity file /home/croessner
debug1: Checking blacklist file /usr/share/
debug1: Checking blacklist file /etc/ssh/
debug1: identity file /home/croessner
debug1: Checking blacklist file /usr/share/
debug1: Checking blacklist file /etc/ssh/
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-
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes256-cbc hmac-sha1 <email address hidden>
debug1: kex: client->server aes256-cbc hmac-sha1 <email address hidden>
debug1: SSH2_MSG_
debug1: expecting SSH2_MSG_
debug1: SSH2_MSG_
debug1: expecting SSH2_MSG_
debug1: Host '[roessner1.
debug1: Found key in /home/croessner
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_
debug1: SSH2_MSG_
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.
Changed in gnome-keyring: | |
status: | Unknown → Fix Released |
Changed in gnome-keyring: | |
status: | Unknown → Incomplete |
Changed in gnome-keyring: | |
importance: | Unknown → High |
status: | Incomplete → Unknown |
Changed in gnome-keyring (Fedora): | |
importance: | Unknown → Medium |
Description of problem:
Some rawhide update today broke ssh, but I can't work out what! I tried backing down openssh to an earlier release, but that didn't fix it. Reporting against openssh anyway.
As a regular user, ssh fails with:
buffer_get_ret: trying to get more bytes 4 than in buffer 0
buffer_get_int: buffer error
(Really helpful error message, NOT! Try googling for:
"buffer_get_ret: trying to get more bytes 4 than in buffer 0"
to see how common it is!)
As root, ssh to the same target works.
Version-Release number of selected component (if applicable): 5.1p1-6. fc11.x86_ 64
openssh-
How reproducible:
100%
Steps to Reproduce:
1.ssh -vvv bock
2.
3.
Actual results: .ssh/known_ hosts:57 SERVICE_ REQUEST sent SERVICE_ ACCEPT received
...
debug1: Host 'bock' is known and matches the RSA host key.
debug1: Found key in /home/ellson/
debug2: bits set: 514/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_
buffer_get_ret: trying to get more bytes 4 than in buffer 0
buffer_get_int: buffer error
Expected results:
1. Working ssh.
2. Greatly improved errors messages!
Additional info: