On Fri, 18 Sep 2015 17:09:43 +0200 Guilhem Moulin <guil...@guilhem.org> wrote:
> Control: tag -1 moreinfo
>
> Hi there,
>
> I wonder what's the best way to close this. dropbear and openssh-client
> can currently coexist, because the SSH clients have different binary
> names: /usr/bin/dbclient and /usr/bin/ssh. We could also install
> dropbear SCP binary to e.g., /usr/bin/dbscp to have a non-conflicting
> SCP *client*.
>
> However that doesn't for the *server* part, since AFAIK a remote
> executable called ‘scp’ is required by the SCP protocol (and needs to be
> in the remote $PATH). So I believe the options at hands are:
>
> * ask the OpenSSH maintainers to consider using an alternative for
> their scp binary (and possibly ssh too), or
> * provide a new package dropbear-client to ship /usr/bin/{dbclient,scp}
> and make it conflict with openssh-client.
>
> Any thoughts or suggestions?
>
Hi Mr. Moulin,
I came across this report while I was trying to get Ansible working
with dropbear.
I know you've wanted to get some suggestions last year but this bug
report, which is only followed by a couple users like me who were
affected from the lack of scp, is not really the right place for
getting answer to the questions you have in your mind. My humble
suggestion is you should talk to OpenSSH maintainers on how to proceed
with it and maybe consult debian-devel for policy related questions or
best practices.
Thanks for your consideration and let's hope we'll have a more
comprehensive dropbear for stretch!
