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

Nik Soggia dropbear at niksoggia.it
Sat May 14 01:09:27 AWST 2016


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 and "none" becomes the hostname.

I have two solutions:

- a mini-invasive surgery (adds 0 bytes to the binary) to move the "case 'e'" in cli-runopts.c in the right spot so that -e can accept arguments still doing nothing and printing the warning message as before (see part 2), or
- a full implementation of the -e argument adding 80 bytes of bloat :), in part 3.

personally I like the bloated solution so "dbclient -e $'\x1d'" can bring back the handy '^]' I miss from the old telnet times where escapes were not printable.

I hope you will review my second patch and include it upstream.
Best regards,



More information about the Dropbear mailing list