SliTaz Forum

artifice

Member

Registered: 2015-01-10

Posts: 18

SSH working fine but SCP fails

I've got a slitaz machine on which dropbear runs on startup. I made a key using 'dropbearkey -t rsa -s 2048 -f ~/.ssh/slitazmachine.key' and then I viewed that key using 'dropbearkey -y' and pasted the result into ~/.ssh/authorized_keys on my crunchbang machine.

My crunchbang machine running openssh has its own key pair. That pubkey is imported into ~/.ssh/authorized_keys on the slitaz machine.

slitaz machine ~/.profile contains:

alias ssh='ssh -i $HOME/.ssh/machine.key'

slitaz machine ~/.ssh/config contains:

Host crunchbang.ip.address

IdentityFile /home/slitazuser/.ssh/slitazmachine.key

crunchbang machine ~/.ssh/config contains:

Host slitaz.ip.address

IdentityFile /home/cbuser/.ssh/cbmachine.key

I'm able to ssh from slitaz to crunchbang and vice versa

The problem is with 'scp'

From a terminal on the crunchbang machine, I can push and pull a file to/from the slitaz machine:

> scp file slitazuser@slitaz.ip.address:"/some/destination/folder/"

> scp slitazuser@slitaz.ip.address:"/path/to/some/file" .

From a terminal on the slitaz machine, however, neither works:

> scp cbuser@crunchbang.ip.address:/home/cbuser/file .

> /usr/bin/dbclient: Connection to cbuser@crunchbang.ip.address:22 exited: No auth methods could be used.

> scp file cbuser@crunchbang.ip.address:/destination/folder/

> /usr/bin/dbclient: Connection to cbuser@crunchbang.ip.address:22 exited: No auth methods could be used.

> lost connection

This kept me up to 4am last night and I've got to ask for help.

mojo

Administrator

Registered: 2011-03-29

Posts: 2,174

Re: SSH working fine but SCP fails

The dropbear key format is not the same as openssh key format.

I don't think the dropbear client on slitaz can use the imported openssh key.

The utility dropbearconvert can be used to convert the openssh key to dropbear key and append to id_rsa.

[c]dropbearconvert -h[/c]

I've never tested the scenario of scp dropbear client to openssh server with public key.

I remove dropbear and install openssh on all my machines including slitaz.

Dropbear client doesn't support X-forwarding and dropbear server doesn't support sshfs which I use on all my machines so it is an easy choice for me.

artifice

Member

Registered: 2015-01-10

Posts: 18

Re: SSH working fine but SCP fails

That's actually what I'm leaning toward.. I started thinking I should just install openSSH (around 3am) but at that point I was fixated on trying to solve it. I think I'll try the conversion to see if that's the issue, but will probably install openSSH regardless.

artifice

Member

Registered: 2015-01-10

Posts: 18

Re: SSH working fine but SCP fails

Well, that doesn't seem to have been the problem. I converted the key and imported it into the authorized_keys on the crunchbang machine and I get the same error when scp-ing from a terminal on the slitaz machine. It's something with the authentication method for scp (which is run through dbclient) not matching available methods on the crunchbang machine, but I can't figure it out.