"So you tried to use the computer and it started smoking? Sounds like a Mac to me." - Louis Rossmann īrainSlayer, I'd refer you back to this patch request that I made 3 years ago.ĪFAIK, ed25519 support on dropbear is still not available. BUT, we probably could get away with going with ed25519 and save a lot of space and headache, perhaps?
Always a good idea to refresh it regularly, as much of a pain in the ass as it is. This is the reason why a reset to defaults is advised every so often, to regenerate the key on the router.
RSA has to be 4096 bit length to be secure. Rsync -avz -e “ssh -i /root/.ssh/id_rsa” some-file-here.From what I understand, ed25519 is fast, secure, and has a small footprint. Now that ssh works, I can easily perform an automated rsync: Dropbear does not automatically look for it like OpenSSH does. Notice that you need to explicitly specify the identity file on the command line. You should now be able to ssh without a ssh -i ~/.ssh/id_rsa Ensure that permissions on this file are set to 600. Now copy or (concatenate) ‘authorized_keys’ to ~/.ssh on ‘webhost’. Since dropbear stores its keys in different format, it needs to be converted for a standard SSH server:ĭropbearkey -y -f ~/.ssh/id_rsa | grep “^ssh-rsa ” > authorized_keys The goal is to allow ‘nas’ to authenticate to ‘webhost’ using a key instead of a password.įirst, generate your identity key on ‘nas’ This assumes that the OpenWRT device is named ‘nas’ and the remote machine is ‘webhost’. I found plenty of examples on setting up key based authentication using dropbear as the HOST, but not as the CLIENT. In order to rsync files from a remote host using a cron script, this is critical. It turns out that the dropbear ssh client works a bit differently when attempting to use key based authentication.
I ran into a little bit of a hiccup getting my OpenWRT NSLU2 device to automatically rsync to a remote host.
0 kommentar(er)
