Control: block -1 by 875979 On Mon, 05 Sep 2016 at 15:15:46 +0300, Mert Dirik wrote: > 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.
In fact the ‘scp.c’ found in the Dropbear source package comes from
OpenSSH with minor modifications, so it makes little sense to ship a
second version the scp binary.
After discussion with upstream and the OpenSSH maintainers, we agreed on
a solution:
1. ship OpenSSH's /usr/bin/scp in a dedicated binary package (unlike
/usr/bin/ssh it only depends on libc6), cf. #875979;
2. make dbclient(1) accept (as no-op) the options passed by scp(1) to
avoid warnings: `-x -oForwardAgent=no -oPermitLocalCommand=no
-oClearAllForwardings=yes`; and
3. for the client part, ship a `dbscp` shell wrapper invoking scp(1)
with dbclient(1) as SSH client.
See https://lists.debian.org/debian-ssh/2017/07/msg00019.html for
details.
--
Guilhem.
signature.asc
Description: PGP signature
