5 ms·
We're talking about two different passwords - the password to your rsync.net account and the passphrase to (duplicity/borg/restic/etc.) that you used to create
by rsync 4y ago
We're talking about two different passwords - the password to your rsync.net account and the passphrase to (duplicity/borg/restic/etc.) that you used to create your failsafe backup here.
If you use an SSH key with a passphrase, etc., to access rsync.net that could, indeed, be an authentication that you lose because your phones and laptops and yubikeys burn in a fire.
But if you can authenticate to a human being, which you can here (after a lot of probing and testing), then the only thing you need to remember is your borg passphrase. Or duplicity. Or gpg pipelined through tar ... or whatever.
- mst 4y agoAlso, for a bunch of cases, you can use something akin to a multi-step ceasar cipher. Yes, the obvious case of e.g. rot13 isn't exactly helpful security wise, but if you select e.g. 4, 22, 18 as the rotation order now you only need to be able to memorise -that- to get your passphrase back from an otherwise unmarked file lying around in the same (or other) storage. Obviously, think hard about your threat model for that one, but if (as I keep procrastinating) I ever put backups of such stuff on something like rsync.net I'd give something akin to that approach serious consideration as being an acceptable trade-off overall.
- nicoburns 4y agoRight, but alternatively you could register an account with a password manager, use a (long) pass phrase as the password for that, and store all your other credentials in the password manager. That way you have full access with only a single pass phrase needing to be remembered, and customer support not required…