> Bump to get this in for 5.9 so users aren't confused by the changed
> default and the resulting incorrect manpage.
> If no one thinks it should go in for 5.9, I'll wait for unlock to poke again.
Thanks for caring about this, Tim.
We should fix the current situation one way of the other. duplicity
users on OpenBSD should speak up. Does the default ssh backend,
paramiko, prevent you from easily using duplicity on OpenBSD-current?
Looks like paramiko can now use the default sshd config.
I don't know what used to be broken with paramiko. I ran through basic
usage with the paramiko backend. I can do full and incremental backups,
restore files, get the file list, collection status, and verify
collections. The only thing it can't do is use ed25519 keys. RSA