After installation of dropbear with +multicall various slinks are created. among thos dbscp. When the server is running and a scp is initiated from a host with openssh, the scp fails with an error about missing scp. A simple slink scp->dropbearmulti fixes the issue. Reproducible: Always Steps to Reproduce: 1. Setup dropbear[multi] on a server 2. scp from client with openssh 3. Error-Msg: bash: scp: command not found Actual Results: Connection is closed Expected Results: successful scp transfer As soon as a link scp -> dropbearmulti is established (even though not listed by dropbearmulti) scp works as expected.
we do not take control of the "scp" program name because openssh owns it and we don't want to conflict (so they can be installed at the same time). we rename dbscp to scp explicitly for that in dropbear. when you run scp (openssh or dropbear), it requests the "scp" subsystem explicitly which runs the "scp" program. i don't think the CLI allows you to change that so you can't tell it to run "dbscp". this isn't related to USE=multicall or the client used. there isn't a good option here.
(In reply to SpanKY from comment #1) > we do not take control of the "scp" program name because openssh owns it and > we don't want to conflict (so they can be installed at the same time). we > rename dbscp to scp explicitly for that in dropbear. > > when you run scp (openssh or dropbear), it requests the "scp" subsystem > explicitly which runs the "scp" program. i don't think the CLI allows you > to change that so you can't tell it to run "dbscp". > > this isn't related to USE=multicall or the client used. > > there isn't a good option here. It's been a while since I stumbled over this. If I remember correctly, the problem back then was, that openssh (client) requested the scp subsystem, but dropbear named it's secure copy tool dbscp and refused to cooperate. However once it was named scp (or rather an scp link existed for the multicall version) things worked as expected. I do see the problem with the conflicting names of openssh. I wonder why it isn't possible to configure a subsystem to executeable mapping (in dropbear), kinda like an aliasing.
(In reply to Sven E. from comment #2) it might be possible to have dropbear exec scp and if that fails, fallback to execing dbscp. it's been a while since i poked around the code though tbh.
