Re:Backblaze: “Why does the private key still need to be sen...
by eric__cartman on Sunday August 29, 2021 @03:37PM
(#28349774)
Personally I split everything into equally sized tar.gz files, encrypt everything with gpg and upload it using rclone. It should be easily doable and scriptable in any Unix-like machine. It's not the fastest way of doing this, and very inconvenient if you need to access the data often. I only use this for off-site archiving that I will never use unless something catastrophic happens.
[ Parent
| on HN ]
Re:Backblaze: “Why does the private key still need to be sen...
by spinax on Sunday August 29, 2021 @04:04PM
(#28349993)
You've basically just described duplicity with rclone as the backend (their term). I personally add duply in front for usability (it handles your includes, excludes, "profile", etc.). Restoring is easy with these 3 working in tandem, and you can manually extract the data as needed for SHTF - just gpg encrypted tarballs. duply runs duplicity who runs rclone in a soundbite.
Re:Backblaze: “Why does the private key still need to be sen...
by 1630269196 on Sunday August 29, 2021 @04:35PM
(#28350227)
I used to do something similar, but these days I either just use rclone's crypt backend (folder hierarchy is kept intact, files encrypted and filenames obfuscated), or a Restic repository hosted on an rclone backend.
Re:Backblaze: “Why does the private key still need to be sen...
by danuker on Sunday August 29, 2021 @03:58PM
(#28349942)
> I will never use unless something catastrophic happens
Have you ever tried to restore from one such archive?
Re:Backblaze: “Why does the private key still need to be sen...
by eric__cartman on Sunday August 29, 2021 @04:16PM
(#28350093)
Yes, it's quite easy. Once all the gpg files are decrypted, the tar archives can be uncompressed with any piece of software that supports tar archives.