Public bug reported:
I connect, over a shared NAT router, to many different servers with ssh.
This works great on Dapper.
After upgrading to Feisty or Gutsy, previously working ssh session
configs (~/.ssh/config) can no longer connect.
Feisty or Gutsy CAN connect to each other, or to a Dapper system, but
not outside machines.
This is NOT an OpenSSH problem. See below.
I do NOT have the seahorse package installed. There is a similar report
to this related to the seahorse package.
I have two Gutsy and one Dapper machine on one GigE subnet and they
route through a Linksys NAT FW/router. All three machines have
(virtually) the same "dpkg -l" output, although the versions are
different, and they have the same network setup (DNS, mask, default
gateway, NIC MTU, etc).
In accordance with the OpenSSH.org web, I have played with MTU on the
NICs and NAT router (1500 on all). Dapper's ssh works fine no matter
what MTU is set on its NIC or the (same) router. I set the router back
to 576 and Dapper ssh sessions work fine. That doesn't appear to be the
problem.
Here's the -vv from a Gutsy machine:
OpenSSH_4.6p1 Debian-5build1, OpenSSL 0.9.8e 23 Feb 2007
debug1: Reading configuration data /home/XXXX/.ssh/config
debug1: Applying options for work-dev
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to work-dev [XXX.XXX.XXX.XXX] port XXXXX.
debug1: Connection established.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug2: key_type_from_name: unknown key type '-----END'
debug1: identity file /home/XXXX/.ssh/identity type -1
debug1: identity file /home/XXXX/.ssh/id_rsa type -1
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug2: key_type_from_name: unknown key type '-----END'
debug1: identity file /home/XXXX/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.7.1p2
debug1: match: OpenSSH_3.7.1p2 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.6p1 Debian-5build1
debug2: fd 3 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
It will hang there forever.
Feisty hangs at the same place.
I built openssh 4.3p2 on Gutsy (same rel as Dapper). I verified 4.3p2
under Gutsy, but see the same problem as 4.6p1. This eliminates OpenSSH
I think.
OpenSSL? Libc? Kernel?
Fix it and I promise I will name my next child whatever you say.
** Affects: ubuntu
Importance: Undecided
Status: New
--
openssh clients on 7.04+ do not work with some ssh2 servers, while 6.10's ssh
does.
https://bugs.launchpad.net/bugs/160760
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
