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:
Is their an argument for me to get debug info printed to the stdout?
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.
WinSshFS
Dokan driver
Environment
Server Environment
Support
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:
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:
Thanks for your time, I'd really like to try to get this working.