https://bugzilla.novell.com/show_bug.cgi?id=818507 https://bugzilla.novell.com/show_bug.cgi?id=818507#c2 --- Comment #2 from kenneth zadeck <zadeck@naturalbridge.com> 2013-05-06 16:36:26 UTC --- I do not think that anyone knows what the bug is. You need to bring two things together to answer what kind of question. you need someone with the skills to diagnose this bug and you need a network where the connections are failing. I work for a large company and have no access to the internals of my company's backbone network. Nor do i have the skills or the time to tear into this problem. I think that it is possible that this is a firewall/router problem, but there are discussions that seem to indicate that the effected machine is sending out a packet that is bad in a way that only a few routers bother to check. There are several threads that indicate that just the length of the list of ciphers can trigger the failure. if that is the case, it seems less plausible to blame the routers. There is a blog that seems to summarize what is known about this bug. http://www.held.org.il/blog/2011/05/the-myterious-case-of-broken-ssh-client-... However, even if it is an overly zealous (brand, version, setting of) router, you are stuck with the problem that ssh does not work in these environments and fixing those routers that are buried in some corporate/university infrastructure is generally not an option. As i said, i mostly submitted this bugzilla so that it would be easy for others to find the workaround. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.