You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this is more to do with the backup method. Services like Dropbox, Amazon and git are all behind user/pass walls.
The only method we really have to worry about is with backing up to a fileshare. But again, I think the responsibility falls on the user to have a secure location to backup the data to. The fileshare should have network permissions assigned to it to allow only the user to access it.
We may need to allow a user/pass to be entered to authenticate with an access control system to be able to save the backup to the restricted folder.
The backups files could also be zipped up with a archive-level password (ie rar does this). However downside with this is that systems would need rar, and tar wouldn't work.
Other option would be to use encryption, which i believe is the best option because:
It's available freely
Easy to use, via CLI
Can automate
Less flaws then zip-level password
Available: ccrypt (-e -Kkey to encrypt with key) (-d -Kkey to decrypt with key)
gpg (The GNU Privacy guard - similar CLI as above, can also do signatures)
Backups should be protected so that only the user that the backup belongs to can see/import the contents.
The text was updated successfully, but these errors were encountered: