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.
