Installing SCP

hey all, new to linux and drobo but really loving first impressions.

please bare with me while i ask seemingly simple questions.

i got ssh installed through dropbear, but that doesn’t have the scp package.

is there a way to enable/install the most common packages found on linux?

also what is the best way to edit files from command line?
i’d love it if i could use an external editor but am not sure how.

thanks for any help!

Hmm. I haven’t used droboapps at all, cause my drobo is not directly connected to the internet (its hooked up to my linux server so I do all this manually) but from my recollection SCP (or at least SFTP) desn’t require any further packages. As long as you have working SSH access, you should just be able to connect to it…

the version of dropbear distributed on the FS does not support SFTP or SCP.

is it possible to install openssh instead?

should be if you can get a version for ARM, this is on my list of todos, but haven’t gotten to it yet.

Any update on this? I’d kill for some sort of SCP support on the Drobo FS. I’m actually quite floored the version of dropbear being distributed doesn’t have it built-in.

If only I was more comfortable cross-compiling ARM code…

Have a look at the developer forum. I made a whole series of posts about cross-compiling that should be quite easy to follow.

I’m aiming at getting openssh compiled pretty soon, although I am quite busy at the moment.

Okay, so on a whim and still riding a high after compiling an updated transmission client, I decided to give this a shot expecting total failure. I managed something a little different.

I downloaded OpenSSH 5.6p1 and dropped into my cross compile environment. I managed to produce statically linked binaries against OpenSSL 0.9.8p. I transfered them onto my DroboShare and was shocked to discover that they seem to actually work.

Here’s the deal. Busybox expects to find sftp-server in /usr/libexec which is part of /dev/root, so all you have to do is make that directory and drop it in there. The binary is 665K in size, which should be 2% of the available space. I don’t know if the binary would survive a firmware update, so I’d advise keeping a copy of it on the drive pack just to be safe. The other binaries such as scp just need to be in the path somewhere, so you can put them on the drive pack rather than take up more flash memory. I have the coreutils package installed, so I just stuffed them in there.

I only did some quick transfer tests with the binaries. I have absolutely no idea how stable they are, so if you decide to use them, [color=#FF0000]you do so at your own risk[/color]! (enough emphasis for you? :))



Oh man, I really wish I’d found those postings earlier. Now that I know about them, I’ll have to get the TransmissionBT instructions posted there.

First of all, gratz on the successful compile.

Can I convince you to write a mini howto? It would be awesome to be able to reproduce this, even with later versions of OpenSSH.

Isn’t a soft-link enough? I was thinking of having a folder in the DroboApps share and link the binary from there.

Yeah, I should probably advertise those posts a bit more on the non-developer community forum… although I think most of it is too technical for the average user.

Please do write a how to. I was just about to try it myself so I could apply the HPN-SSH patch for OpenSSH (I’m going to plug HPN-SSH - 1 to 2 orders of magnitude performance increase over stock OpenSSH).


Actually, I went idle on writing a how-to because some one already did. You can find it here:

The how-to is centered on DroboFS, but the instructions should apply just as well for a Droboshare.