Would anyone be able to point me to a guide or how-to that describes how to use an SSH backend?
An url-encoded SSH private key. The private key must be prefixed with sshkey://. If the file is encrypted, the password supplied is used to decrypt the keyfile. If this option is supplied, the password is not used to authenticate. This option only works when using the managed SSH client.
I know how to generate RSA keys and how to add them to ~/.ssh/authorized_hosts. What I do not know how to do is to generate a “An url-encoded SSH private key.”
I’m new to Duplicati (another Crashplan refugee) but so far I have been impressed with the program. However, I have still having troubles getting public/private key authentication working. I am using Bitwise SSH server on my destination and I am able to get the private key for the server and public key setup for the user. However, when I try to have Duplicati use the key to login, I am unable to. Can you provide some more detail on the Duplicati setup required?
Edit: I was able to get the private key to work as a file but every time that I tried the URL encoded version in the config, I got an error stating the the file name was too long. Has anyone else experience this? I would prefer not to have the key in a file.
Thanks @kenkendk for the info on how to create an url-encoded SSH private key. How could one do the same thing offline (e.g. using linux setup) so that the private key does not need to be sent to an untrusted website? Kindly, Fred
NOTE: Perhaps Base64 and URL Encoding and Decoding can be used using the 'url encode’ option, when adding the ‘sshkey://’ prefix before adding it as an ‘ssh-key’. This page can be made available offline and still functions. Did not get this to work yet though.