@earthshine precisely that is the poibt of it and also the correct answer to #FUD by #CCSS vendors (i.e. #Microsoft) against #FLOSS (i.e. #Linux)…

• Also #transparency is key, cuz then #Backdoors (i.e. #Govware) like #GoldenKeyBoot are nearly impossible to hide.
  • The middle-ground is #SourceAvailable like #Tarsnap, where providing the client sourcecode is done as means to build #trust with #evidence to claims (in this case 'here's the code, you have custody of all the keys, we never have them!'…

@mrmasterkeyboard that's basically a 3-clause BSD, so obviously not a problem.

I'd not consider it if it was some "source available" #OpenWashing like SSPL or RSAL.

• I mean, I can totally understand why one would not do release something as #FLOSS (I.e. #Tarsnap is #SourceAvailable as a means to evidence to it's customers that it truly has #SelfCustody and that they hold no keys to the encrypted data)...
  • Even if that means like #DolphinProject [when there was that huge Nintendo Leak] I cannot even look at Tarsnap's source code!

@decryption that's a good deal, m8.

Personally, I want to #DIY myself something like #Tarsnap (which is why I refuse to look at it's source code!) but with custom endpoints to store stuff in...

• Simply because I can't use anything subject to #CloudAct (i.e. #amazon #S3 / #Glacier) and want something uniformly that can do "pull backups" without anything on the machines that I want/need to backup / restore.

  • Plus not being chained to a #centralized. #SingleVendot / #SingleProvider solution is kinda important.

I mean, without #GDPR, #BDSG (if not even stricter rules and a moody US Government) I'd be more inclined just to pay for Tarsnap et. al. cuz @cperciva made a really good service with it...

@mulbox @dalai @jwildeboer other options are:

• borg
• bacula
• amanda
• rdiff-backup
• rclone
• rsync
• duplicity, incl. it's easy-to-use frontend: #DejaDup - available on @ubuntu / #Ubuntu
• if those are small files that are frequently changed and/or they want to collab, then maybe using git is a better alternative.

Same with backup strategies, budget, storage amount and performance requirements.

• Most of these tools can target/source any mounted filesystem, some even deal with #S3-Storage. If #privacy and #DataProtection ain't a concern and the storage itself does deduplication and compression, just regularly making tar (or pax) archives and shoving them over to the #iSCSI / #NFS / #SMB / #SSH / #FTP server is also an easy option.

• If they don't want any onsite storage, ain't subject to #GDPR and don't mind #CloudAct, but rather want to solve the problem with a #CreditCard, I'd recommend #Tarsnap by @cperciva, as it's a solid product with published source available...

Personally I touched #borg and I do think that #rdiffbackup's reverse-delta approach is good if you have growing datasets, but sometimes stupid pipes and cron'd scripts will do just fine.

@trezzer #Tarsnap is end-to-end encrypted, using Amazon storage buckets on the backend, and reasonably priced. https://www.tarsnap.com

I also like rclone, which was mentioned.