Problems with SCP and dropbear

[althalus]

So I got my Pi yesterday, got Core installed, dropbear set up and running, and starting to play with it. I'm not a fan of the debian import script, it seems to be pulling in all sorts of dependencies that I wouldn't need in TC on my laptop (eg, selinux). So I'm trying to set up my build tools (the tc-ext-tools shell scripts) - but I can't seem to use scp to get anything on or off the pi.

From my laptop:

Code: [Select]

tc@box:~/PROJECTS$ scp tc-ext-tools/ tc@10.1.1.6:

Secure login powered by Dropbear SSH server on piCore.
Enter passphrase for key '/home/tc/.ssh/jls.identity':
sh: scp: not found
lost connection

From the pi:

Code: [Select]

tc@box:~$ scp -r tc@10.1.1.2:PROJECTS/tc-ext-tools ./PROJECTS/
/usr/bin/dbclient: No such file or directory


[curaga]

Just to make sure, it's dropbear.tcz not an imported dropbear?

(I don't have a pi, just clarifying)

[althalus]

Yep, dropbear.tcz.

[althalus]

Actually, if I'd looked closer at the error messages that posted, I could have solved this quicker. Putting symlinks to dropbearmulti in /usr/bin successfuly worked around the problem. Note that I ALSO needed the extra scp symlink in /usr/bin for scp TO the pi to work.

 I think this should qualify as a bug in the dropbear.tcz package?

[tinypoodle]

Note that I ALSO needed the extra scp symlink in /usr/bin for scp TO the pi to work.

 I think this should qualify as a bug in the dropbear.tcz package?

Do you mean on the pi or on the box connected to it?
In latter case, which arch is that?

[bmarkus]

 I think this should qualify as a bug in the dropbear.tcz package?

Thanks for reporting. There is a new version available, will update package.

[althalus]

Note that I ALSO needed the extra scp symlink in /usr/bin for scp TO the pi to work.

 I think this should qualify as a bug in the dropbear.tcz package?

Do you mean on the pi or on the box connected to it?
In latter case, which arch is that?

On the Pi, apologies if that wasn't clear.

[tinypoodle]

The "ALSO" in caps was what confused me...   
An instance of scp is required to run concurrently on both sides (auto invoked on remote machine).

[althalus]

The "ALSO" in caps was what confused me...   
An instance of scp is required to run concurrently on both sides (auto invoked on remote machine).

Yeah, but having scp in /usr/local/bin isn't good enough. What it seems like to me, is that the problem when using scp from the pi has something to do with dropbear itself being hardcoded to expect dbclient in /usr/bin, and the problem of using scp to the pi seems like a path issue, like /usr/local/bin isn't listed in where ever the $PATH variable is set when using scp.

At any rate, I have a workaround, and I've shared my experience so smarter people can fix it

[sbp]

 I think this should qualify as a bug in the dropbear.tcz package?

Thanks for reporting. There is a new version available, will update package.

Hi bmarcus

I didn't know that scp was possible using dropbear. When you find the time please update the package.

Steen

[tinypoodle]

I didn't know that scp was possible using dropbear.

Code: [Select]

dropbearmulti

[paco]

Hello all,

after reading this post, I found some websites indicating, that dropbear runs with "sftp-server". There is a "sftp-server.tcz" for x86. Would it be possible to add sftp-server to the RaspPi port?

Thanks,
Patrick

EDIT: I just found that openssh.tcz exists and sftp-server is inside this packet. To use sftp, I just use openssh instead of dropbear.