Busybox/Dropbear - Channel was Closed.

[drbenway6667]

WinSshFS

• stable
• prerelease
• custom build
• Version: <1.6.1.13>

Dokan driver

• stable
• prerelease
• custom build

Environment

• Windows version: <10>
• Architecture: x64
• Related software: fresh install

Server Environment

• Linux 3.0.8 armv71
• BusyBox v1.20.2 in /bin/busybox

Support

• Usage: personal
• Your personal priority to solve this issue: top
• Support ability: can debug on remote host

---

Trying to mount a remote share on a server running Dropbear v2016.74 on non-default port with password authentication, no proxy server and all other default settings results in the following error on both stable and prerelease branches:

name could not connect:
Channel was Closed.

I have a feeling it may be an issue with the default busybox on the box, I have a custom binary running on the device located at another path, but do-not have write access to /bin to replace the original binary. My questions are:

1. Is their an argument for me to get debug info printed to the stdout?
2. Is their a way for me to run the application with the busybox binary located in a place other than /bin/busybox?

Thanks for your time, I'd really like to try to get this working.