Commented Issue: SCP fails with dropbear because of option -q [1164]

<p>SCP transfer uses commands like this</p>
<p>channel.SendExecRequest(string.Format(&quot;scp -qpf \&quot;{0}\&quot;&quot;, filename));</p>
<p>When the remote system is using dropbear, the command fails with a usage message. </p>
<p>&nbsp;</p>
<p>By default the scp command in dropbear is compiled without progress meter. Unfortunately in this case it does not ignore option &quot;-q&quot; but it complains with a usage message.</p>
<p>&nbsp;</p>
<p>I compared with the commands sent by WinSCP &quot;scp -r -p -d -f filename&quot; and the scp command from openssh &quot;scp -f filename&quot;. It doesn&#39;t seem do be necessary to specify option &quot;-q&quot; for the remote scp.</p>
<p>That&#39;s why I propose to remove option &quot;-q&quot; from all scp commands.</p>
<p>&nbsp;</p>
<p>Additionally the ScpClient seems to wait without timeout (or with a very long one) when it does not receive any data as a result of the failed remote scp command.</p>

Comments: ** Comment from web user: olegkap **

Please check 22112 commit where I remove -q flag and see if it works.
What I am wondering about is if combine option will work or they need to be sepearted like -r -p -d
Thanks,
Oleg