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