Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to implement backup security #26

Open
hamstar opened this issue May 5, 2012 · 2 comments
Open

How to implement backup security #26

hamstar opened this issue May 5, 2012 · 2 comments
Labels

Comments

@hamstar
Copy link
Owner

hamstar commented May 5, 2012

Backups should be protected so that only the user that the backup belongs to can see/import the contents.

@hamstar
Copy link
Owner Author

hamstar commented May 9, 2012

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.

@bhavicp
Copy link
Collaborator

bhavicp commented May 10, 2012

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:

  1. It's available freely
  2. Easy to use, via CLI
  3. Can automate
  4. 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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants