Duplicity VS age

http://duplicity.nongnu.org/ at least can use PGP public keys. I've used it for a long time and not seen any particular reason to change.

There are backup tools with built-in encryption like borg backup or duplicity, these should be fine. If you already have a backup process and it's missing encryption then you should be able to use e.g. age or gpg.

For my family photos (critical, irreplaceable, on plex), I use duplicity which can make use of Amazon Glacier and Deep Archive for really cheap storage (0.00099 /gb /month no joke) with incremental versioning and client side encryption. Long restore time, but perfect for disaster recovery on data that doesn't change much. Want to set up the same for music (which rarely but sometimes changes, e.g. Correcting tags).

And google docs / apple cloud etc. aren't proper backups. They can cancel your account, be inaccessible, or hacked even. There's software like duplicity that can upload encrypted backups to multiple services, which are handy. But in any case, if you're doing cloud backups, do do redundant local backups too. My setup is I've a USB stick tacked onto a Raspberry Pi computer, and use something called borg to do daily backups over SSH.

I have had good success using [Duplicity](http://duplicity.nongnu.org/) via [Duply](https://www.duply.net/) for a few years now. The main point for me is that duplicity directly backs up to many cloud-storage endpoints. I'm using google drive specifically, but it supports a ton of options.

and echoing the result after converting to an age private key

I like that https://github.com/FiloSottile/age has small public keys.

> something fresh

It exists, it's called age..

Some random links

https://github.com/FiloSottile/age

https://www.reddit.com/r/crypto/comments/hr64hr/state_of_age...

https://github.com/FiloSottile/age/discussions/432

> (Acquiring keys, rotating keys, identifying compromised keys, and most importantly either reaches a large enough percentage of emails..

Oh nevermind, age doesn't do any of that. Indeed, it doesn't even do email https://github.com/FiloSottile/age/issues/93

Encrypted secrets thanks to SOPS and Age

I never heard of "Age" before this post. Thank you to share. If others are interested to learn more, here are two other interesting posts about Age:

https://github.com/FiloSottile/age/discussions/432

https://words.filippo.io/dispatches/age-authentication/

of all things I was able to resolve the issue via this github issue: https://github.com/FiloSottile/age/issues/370#issuecomment-1...

Why keep something secret on a public repo? Is that not an oxymoron?

Also, I’m terms of encryption something like age[0] makes it much easier to not shoot yourself in the foot.

[0] https://github.com/FiloSottile/age

Why RSA specifically? For backups, I recommend Tarsnap. But if you really don't want to pay for encrypted cloud hosting, then check out age encryption.

I wouldn't use OpenSSL personally. If you just need simple but secure symmetric encryption, checkout the scrypt(1) encryption utility from Tarsnap. If you need support for public keys, check out age(1).