Hi,
It sounds like you have a symlink from /usr/bin/scp
to a non-multi dbclient binary, instead of a symlink to the
dropbearmulti binary?
Cheers,
Matt
On Mon, Apr 09, 2012 at 11:16:15AM -0400, Ian McDonnell wrote:
> Matt,
>
> Thanks for a quick reply. I have two traces from the client side,
>
Matt,
Thanks for a quick reply. I have two traces from the client side,
one talking to my old target running dropbear 0.50 and another
trace talking to dropbear 0.55 target. In both cases, the openssh
client appears not to be using the 'subsystem' mechanism and
is simply directing the server-end
Hi,
There isn't any scp specific code, so I think something else
must be going wrong. Does running "ssh tsct hostname" work?
(scp gets run as a command argument like that).
Could it be that 0.55 was compiled against a different libc
that has dependencies on libnss* or something? To me it
looks as
All,
I've moved from version 0.50 to 0.55 and find that I can login
just fine using openssh client ssh and dropbear 0.55 server, but
when using openssh client scp to the same dropbear server the
command fails with:
> $ scp Makefile tsct:
> toor@tsct's password:
> WARNING: Ignoring unknown argu
