Launchpad has imported 14 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=484459.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2009-02-06T22:27:00+00:00 John wrote: 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): openssh-5.1p1-6.fc11.x86_64 How reproducible: 100% Steps to Reproduce: 1.ssh -vvv bock 2. 3. Actual results: ... debug1: Host 'bock' is known and matches the RSA host key. debug1: Found key in /home/ellson/.ssh/known_hosts:57 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_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received 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: Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/0 ------------------------------------------------------------------------ On 2009-02-06T22:51:00+00:00 John wrote: The problem seems to be caused by my id_dsa key ??? Removing that and the id_rsa key works fine. I use that dsa key in a lot of places, so I don't want to remove it permanently. Whats going on? A working rsa public key: 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_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/ellson/.ssh/id_rsa (0x2880550) debug3: input_userauth_banner Same site, with the id_dsa & id_dsa.pub restored into .ssh/ 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_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received buffer_get_ret: trying to get more bytes 4 than in buffer 0 buffer_get_int: buffer error Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/1 ------------------------------------------------------------------------ On 2009-02-09T11:18:43+00:00 Tomas wrote: What have you upgraded - client or server? What is the openssh version on the other end? What happens if you do 'unset SSH_AUTH_SOCK' before running the ssh client? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/2 ------------------------------------------------------------------------ On 2009-02-09T12:22:23+00:00 Tomáš wrote: Same here, today's rawhide, cannot connect from client to server. client: openssh-5.1p1-6.fc11.x86_64 openssl-0.9.8j-7.fc11.x86_64 glibc-2.9.90-3.x86_64 gcc-4.4.0-0.16.x86_64 server: openssh-5.1p1-6.fc11.i386 openssl-0.9.8j-6.fc11.i686 glibc-2.9.90-3.i686 gcc-4.3.2-7.i386 Removing ~/.ssh/known_hosts didn't help. Unsetting SSH_AUTH_SOCK helped. $ echo $SSH_AUTH_SOCK /tmp/keyring-c543Ad/socket.ssh So... this looks like gnome-keyring error :-/ Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/3 ------------------------------------------------------------------------ On 2009-02-09T12:29:05+00:00 Tomas wrote: Yes, if unsetting SSH_AUTH_SOCK helps and it points to gnome-keyring and not regular ssh_agent it is gnome-keyring bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/4 ------------------------------------------------------------------------ On 2009-02-09T18:07:58+00:00 John wrote: Using ssh from a ssh login session, without a desktop and with no SSH_AUTH_SOCK set, works ok. When I get back home tonight I'll see if SSH_AUTH_SOCK is set and if unsetting it helps me, but that seems likely based on Comment #4. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/5 ------------------------------------------------------------------------ On 2009-02-09T18:10:38+00:00 John wrote: Oh yes, only my client was updated to fc11 rpms. The servers are all fc10 or less. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/6 ------------------------------------------------------------------------ On 2009-02-09T22:52:51+00:00 John wrote: Confirming "unset SSH_AUTH_SOCK" fixes the issue for me too. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/7 ------------------------------------------------------------------------ On 2009-02-14T00:28:44+00:00 Matthias wrote: What version of gnome-keyring ? What arch ? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/18 ------------------------------------------------------------------------ On 2009-02-14T01:47:45+00:00 John wrote: gnome-keyring-2.25.90-4.fc11 x86_64 I can't reproduce this bug on a similarly equipped i386 box. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/19 ------------------------------------------------------------------------ On 2009-02-14T01:57:27+00:00 John wrote: Reverting to gnome-keyring-2.25.5-1.fc11.x86_64 make ssh work again, although it gives an error message: ellson@ontap:Desktop> ssh penguin Error reading response length from authentication socket. Last login: Fri Feb 13 20:43:53 2009 from ontap.ellson.com ellson@penguin:~> Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/20 ------------------------------------------------------------------------ On 2009-02-15T01:14:43+00:00 Matthias wrote: Can you retry with 2.25.91 ? It contains some more 64bit fixes. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/21 ------------------------------------------------------------------------ On 2009-02-15T12:46:19+00:00 John wrote: Everything seems to work with gnome-keyring-2.25.91-1.fc11.x86_64 Thanks Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/22 ------------------------------------------------------------------------ On 2009-06-16T05:57:33+00:00 Einer wrote: Hey Guys, the bug is back in version gnome-keyring-2.26.1-1.fc11.x86_64 Symptoms/process same as above postings. Fedora 11 x86_64 Einer Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/328277/comments/26 ** Changed in: gnome-keyring (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/328277 Title: can not login using ssh anymore Status in GNOME Keyring: Unknown Status in gnome-keyring package in Ubuntu: Fix Released Status in gnome-keyring package in Fedora: Fix Released 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 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 [email protected] debug1: kex: client->server aes256-cbc hmac-sha1 [email protected] 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. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/328277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
