3 ms·
The restic team refuses to have unencrypted backups just "because security". I hate such an approach when someone assumes that whatever happens their opinion i
by BrandoElFollito 3y ago
The restic team refuses to have unencrypted backups just "because security".
I hate such an approach when someone assumes that whatever happens their opinion is the best one in the world and everyone else is wrong.
I do not want to encrypt my backups because I know what I am doing and I have very, very good reasons for that.
Restic could allow a --do-not-encrypt switch and backup by default.
The arrogance of the devs is astonishing and this si why I will not use Restic and i regret it very much because this is a very good backup solution.
Try Borg.
- arisudesu 3y agoMind sharing the reasons?
- petre 3y agoBackup locally or on a NAS, don't worry about losing the keys and all of your backups. I'm using duplicity because none of these can sync to a rsync server that I run on my NAS.
- BrandoElFollito 3y agoYou listed the main reasons, thanks. As for remote backups - I use ssh with Borg and it works fine. If this is a NAS you can probably enable ssh (if it is not enabled already). BTW for my remote backups I do encrypt them but this is a choice the author of Borg left open. There are other issues with Borg such the use of local timestamps (naive date format, no timezone) instead of a full ISO8601 string, and the lack of capacity to ask whether a backup is completed (which is a nightmare for monitoring) because the registry is locked during a backup and you cannot query it.