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?
Cheers,
--
Guilhem.
signature.asc
Description: Digital signature
