/srv/irclogs.ubuntu.com/2014/04/06/#ubuntu-devel.txt

=== sraue_ is now known as sraue
Kalidarnthere was an ssh update recently wasn't there?06:35
Kalidarnfor some strange reason I cannot ssh into any of my cisco routers anymore with the ssh client on ubuntu06:37
Kalidarnafter this update: openssh-client:    amd64 (6.6p1-1, 6.6p1-2)06:37
Kalidarnworks with putty but i get connection refused with regular openssh06:37
Kalidarni've narrowed it that it must be the ssh client, because it works from other machines, and works from the same machine if i use putty06:40
Kalidarnhttp://paste.ubuntu.com/7211115/06:40
Kalidarnand i know it used to work until very recently.06:40
Kalidarnseems to shut straight after debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP06:42
Kalidarnwhere as on my other machine this happens06:43
Kalidarndebug2: dh_gen_key: priv key bits set: 143/25606:43
Kalidarndebug2: bits set: 512/102406:43
Kalidarndebug1: SSH2_MSG_KEX_DH_GEX_INIT sent06:43
Kalidarndebug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY06:43
slangasekKalidarn: "connection refused" is pretty definitively not a bug in the ssh client06:43
Kalidarnyeah but if it's because some sort of feature is unavailable that it wants maybe the remote host is refusing06:44
slangasekand the only difference between 6.6p1-1 and 6.6p1-2 was a server configuration change06:44
Kalidarndoesn't explain why it works on exactly the same machine with putty instead :P06:44
slangasekno, you said "connection refused".  "Connection refused" means a failure at the tcp level06:44
Kalidarnwhich means it's not an ACL06:44
Kalidarnalso ssh to other things work06:45
Kalidarneg ssh into a freebsd or linux server06:45
slangasekwell, I don't know why you're having problems, but it's not related to the upgrade from 6.6p1-1 to 6.6p1-206:46
Kalidarnhmm.06:46
Kalidarnand initially i would have agreed and thought sure could be tcp issue something blocking it06:46
Kalidarnbut that does not explain why it works with putty on exactly the same system06:46
Kalidarnto the same remote host06:46
slangasekanyway, your pastebin shows it's not actually getting connection refused; it is getting past the initial negotiation, then the server is hanging up06:47
Kalidarnyes which is why i'm rather confused06:47
Kalidarndoesn't seem to like me connecting with openssh06:47
Kalidarnfrom this machine06:47
Kalidarnworks with 6.2p2 from the mac06:47
slangasekif it worked with 6.6p1-1, then something's changed on your server06:47
slangasekand you'll need to debug it there06:47
Kalidarni reloaded the configuration file so nothign has changed there06:48
Kalidarnso nothing has changed there06:48
slangasekyou can always try downgrading the client using the links on https://launchpad.net/ubuntu/+source/openssh/+publishinghistory to verify the last version of the client (if any) that works06:48
Kalidarni only seem to recall it being an issue today06:49
Kalidarni have a trusty vm so ill try it in that06:49
Kalidarn(the downgrade) that is06:49
slangasekthe diff between 6.6p1-1 and 6.6p1-2 is absolutely trivial and unrelated, so if downgrading that fixes it, then we're looking at a miscompilation somewhere06:49
Kalidarnthat's what i'm starting to think06:49
Kalidarncos a network related issue makes no sense if it works in putty06:49
Kalidarnmy originating address would be exactly the same06:50
Kalidarnthat cisco router does have an ACL that only allows certain local IP addresses to connect (but my local IP has not changed)06:50
Kalidarnand as i said I ruled that out by using a different client06:50
Kalidarnis there any way of grabbing the older deb file from that page slangasek?06:51
slangasekyes, you browse the links to the version you want to download06:51
Kalidarnah here we are.06:53
Kalidarnokay so as to be expected that made no difference.e06:56
Kalidarnalthough it is quite well possible i have not tried since installing trusty06:56
* slangasek nods06:57
Kalidarnill try booting a 13.10 vm06:57
slangasekthere's a RH bug report about newer openssh (6.3 and later) failing to talk to ciscos: https://bugzilla.redhat.com/show_bug.cgi?id=102643006:57
ubottubugzilla.redhat.com bug 1026430 in openssh "OpenSSH can no longer connect to Cisco routers/switches" [Unspecified,Assigned]06:57
slangasekthere are some hints there about how to work around it with client options06:57
Kalidarnoh :)06:57
Kalidarnthe description does sound relvant06:58
slangasek(found by searching for '"debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP" cisco', fwiw)06:58
slangasekif that turns out to be the problem, please file a bug against the openssh package in Ubuntu, referencing that one06:58
Kalidarnyeah06:58
Kalidarnslangasek: and i can confirm it works in 13.1007:02
Kalidarni think it might already be lodged as a bug07:03
Kalidarnhttps://bugs.launchpad.net/ubuntu/+source/openssh/+bug/128722207:03
ubottuLaunchpad bug 1287222 in openssh (Ubuntu) "openssh-client 6.5 regression bug with certain servers" [High,New]07:03
Kalidarnand yes doing that solution works slangasek07:08
=== ktosiek_ is now known as ktosiek
cjwatsonslangasek,Kalidarn: I would say if there are workarounds then we should leave it at that.  I'm not at all keen on weakening the OpenSSH client's defaults due to bugs in embedded servers09:03
cjwatson(well, modulo documentation perhaps)09:04
slangasekcjwatson: fwiw the workaround in the RH bug indicates that you can /strengthen/ the defaults for the same result09:04
slangasek(i.e., it's an issue with a buffer limit on the server for kex options, so dropping the weakest solves the problem fine)09:04
cjwatsonupstream's welcome to do that, but similarly this is in the class of things I Do Not Mess With in packaging09:04
* slangasek nods09:05
cjwatson(because doing that means potentially dropping support for other systems and I don't want that to be on my head ... it's a domino trail)09:05
Kalidarncjwatson: yeah I just wrote a shell script that i run09:26
KalidarnsshCisco.sh user@host09:27
Kalidarnfor cisco stuff09:27
Kalidarncalls ssh with the necessary options09:27
Kalidarnhopefully people who start using buntu 14.04 know what is up :P09:28
doko_kirkland, I see your name in a not uploaded facter-plugins tarball. can this package please removed alltogether?12:50
doko_Riddell, shadeslayer_ : please merge the changes from korundum 4:4.11.3-2, we need to remove ruby1.8 in trusty14:39
doko_https://bugs.launchpad.net/ubuntu/+source/korundum/+bug/130336614:42
ubottuLaunchpad bug 1303366 in korundum (Ubuntu Trusty) "korundum needs to remove the ruby1.8 dependencies for trusty" [High,Confirmed]14:42
=== doko_ is now known as doko
dokogeser, libaspectr (0.3.5-3ubuntu2) hardy ... removing now ..17:27
Logan_I like how tty1 keeps logging me out as soon as I log in20:10
dokoRiddell, ScottK, shadeslayer_: it's really bad if you never sync the debian packaging in packages where you are always ahead of debian ...20:24
=== Zic_ is now known as Guest68868
psusicjwatson_, looks like there's another bug in parted I caused by backporting the loop fixes... I called the fat and ntfs probe code from the msdos label probe code because they can be confused with an msdos mbr.. but I think the old code there can't handle !512 byte sector sizes20:53
ScottKdoko: We do periodically.  I'll take a look at it tonight or tomorrow if no one else does.22:01
dokoin this case the period seems to be >= 3 years ;p22:09
ScottKTheir Korundum/Qtruby packages were made from ours, so debian/changelog doesn't tell all.22:15
=== Guest68868 is now known as Zic
lamontThe following packages have been kept back:23:59
lamont  libdb-dev23:59
lamontsaucy->trusty upgrade didn't get rid of it, and it's still being held back...  I wonder if we care?23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!