I ran into the same issue connecting from 13.10 to 12.04. In order to
fix I had to uncomment both the Ciphers line in virbal's fix and the
MACs line.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launc
I have the same problem running Linux Mint Debian Edition 201303
connecting to both an Ubuntu and Red Hat servers. Editing the ciphers
line works for me too.
** Also affects: openssh (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a memb
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New => Confirmed
--
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/17
Got the same problem:
ihanick@bb:~/ecu$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.1 LTS
Release:12.04
Codename: precise
ihanick@bb:~/ecu$ ssh -V
OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
trying to ssh from 12.04 ho
Just as another data point, I can ssh fine from Ubuntu 11.10 and Ubuntu
12.04 to ssh servers running on CentOS 5 (OpenSSH 4.3) and CentOS 6
(OpenSSH 5.3).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.l
Just to note that virbal's fix worked for me connecting to RHEL and
getting the same problem, but by "comment out" he means "make it so that
the Ciphers line *isn't* commented out".
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openss
I have a same problem. In /etc/ssh/ssh_config comment out the line
Ciphers
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-
cbc
It worked for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubu
I have the same problem ssh'ing from a 11.04 box (running openssh 5.8)
to a 10.04 box (running openssh 5.3). I've tried with three different
clients all on the same network, two of with have 11.04 and one of which
has 10.04. All are connecting to the same server Only the 10.04 box is
able to conne
Matt, did you try ensuring that the MTU's are the same on both machines?
Try using tracepath...
tracepath remote.host
Should give some idea.
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This issue still exists for me when trying to ssh from 11.04 box to a
10.04 box.
** Changed in: openssh (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.ne
Got exactly this issue while connecting from Ubuntu 11.04 / ssh 5.8 to
FreeBSD / ssh 5.4
Can easily connect from any other ubuntu out there.
--
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/
Server might be getting DOS'd.
Tweak MaxStartups in sshd_conf
Ken.
From: Paolo Stancato
To: tommymcgui...@yahoo.com.au
Sent: Monday, 1 June, 2009 10:22:11 AM
Subject: [Bug 174168] Re: expecting SSH2_MSG_KEX_DH_GEX_GROUP
Same problem trying to conne
Same problem trying to connect to Github, MTU trick did not help. I'm
running Jaunty
pa...@darkstar:~$ uname -a
Linux darkstar 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:31:32 UTC 2009
x86_64 GNU/Linux
pa...@darkstar:~$ ssh -v g...@github.com
OpenSSH_5.1p1 Debian-5ubuntu1, OpenSSL 0.9.8g 19 Oc
Well, I did not install jaunty, but i recompiled the jaunty sources on intrepid
and also the latest upstream sources (5.2p1). Both show exaclty the same
behaviour for me (ssh hangs with the "debug1: expecting
SSH2_MSG_KEX_DH_GEX_GROUP" message)
The MTU trick did not work for me either. And even
Thanks for taking the time to report this bug. Marking as invalid as two
different statements it is either patched or connected to network
issues. If you feel at any time that this bug is valid on recent Ubuntu
(Jaunty), feel free to reopen this bug again.
** Changed in: openssh (Ubuntu)
St
This solved it for me:
http://www.snailbook.com/faq/mtu-mismatch.auto.html
"You probably have an MTU/fragmentation problem. For each network
interface on both client and server set the MTU to 576, eg ifconfig eth0
mtu 576"
If 576 doesn't work try 1000.
--
expecting SSH2_MSG_KEX_DH_GEX_GROUP
ht
Opps i mean version 5.1
--
expecting SSH2_MSG_KEX_DH_GEX_GROUP
https://bugs.launchpad.net/bugs/174168
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.
The following describes the bug you are having with openssh and says
this will be fixed in version 5.2 they are patches attached to these
bugs, i have not tried them though.
https://bugzilla.mindrot.org/show_bug.cgi?id=1363
--
expecting SSH2_MSG_KEX_DH_GEX_GROUP
https://bugs.launchpad.net/bugs/
18 matches
Mail list logo