Re: Dropbear Digest, Vol 171, Issue 1

Il 16/06/20 06:00, dropbear-requ...@ucc.asn.au ha scritto: Dropbear 2020.79 is now released. Hello, I can't compile DB 2020.79 with uClibc-ng (1.0.32, looking at the 1.0.34 sources nothing has changed) unless I add "#define _GNU_SOURCE" on top of "dbrandom.c" (it is required by

Re: dbclient can't connect to cisco

Il 16/11/18 15:25, Matt Johnston ha scritto: The problem is that waiting for the remote banner is still adding a round trip of delay. That's fine for a local network, but me -> dropbear.nl is half a second, that's no good. As long as we let the Cisco speak first, it is happy. So why don't

Re: dbclient can't connect to cisco

Il 14/11/18 16:13, Matt Johnston ha scritto: I'm not keen on changing dbclient, the current implementation saves a network roundtrip. It's perfectly reasonable according to the spec. If you have Cisco support could you report it to them? Unfortunately I don't have Cisco support. I think

dbclient can't connect to cisco

Hi, openssh can connect to cisco appliances and dbclient can't (but cisco ssh client can connect to dropbear). Thanks to tcpdump I think that I found the problem: openssh sends "SSH-2.0-OpenSSH_7.4 \r\n" cisco sends "SSH-2.0-Cisco-1.25\r\n" openssh sends kexinit cisco sends kexinit, then all

Re: dbclient -e option (part 4 of 3: yes, 4!)

Il 13/05/2016 19:15, Nik Soggia wrote: enjoy! Mailman chewed up the patches. here they are again. Regards, begin-base64 644 dropbear-2016.73.patches.tar.xz /Td6WFoAAATm1rRGAgAhARwQz1jM4Cf/BgRdADIciiK0MVw05AIwZdZ4 /bXMXoPQaplmL8aQpyYaqjR0h4ffYr13XhCT7WF/QyUgJP023d0MHFNKyQqE

dbclient -e option (part 3 of 3: full implementation)

here is the -e full implementation. enjoy! diff -Naur dropbear-2016.73.old/cli-chansession.c dropbear-2016.73.new/cli-chansession.c --- 2016.73.old/cli-chansession.c 2016-03-18 15:44:43.0 +0100 +++ 2016.73.new/cli-chansession.c 2016-05-13 18:55:00.0 +0100 @@ -372,7

dbclient -e option (part 2 of 3: trivial patch)

here is the trivial patch. -e is still a no-op but it will accept arguments --- 2016.73.old/cli-runopts.c 2016-03-18 15:44:43.0 +0100 +++ 2016.73.new/cli-runopts.c 2016-05-13 18:55:00.0 +0100 @@ -297,7 +297,6 @@ break; #endif

dbclient -e option (part 1 of 3: intro)

Hello everybody, today I was fiddling with c-kermit and zssh to test in-band file transfers. Both tools insist adding the "-e none" to the command line arguments to tell openssh to make the session fully transparent. dbclient instead prints its version and quits because treats "-e" as a switch