-
Notifications
You must be signed in to change notification settings - Fork 937
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
Don't touch .ssh and .gnupg with the default settings … #109
Comments
👍 |
1 similar comment
👍 |
👍 Just discovered this behavior after the fact, and I feel pretty violated. Even looking just now, I couldn't find anywhere in the docs that mention that this program uploads private keys by default—I certainly don't consider them "pure configuration files". Glad to see you're sold on the idea of making it non-default (#512), but please at least note this behavior in the main README and Other than that, this is an awesome utility! |
👍 Not clearly and prominently detailing in the main documentation that such sensitive information as a user's .ssh folder would automatically be synced to Dropbox—regardless of whether or not the user's private keys were password-protected—is incredibly careless. Please omit this default behaviour or, at a minimum, include a prominent disclaimer in the README file. |
I've now had to void my private key twice because of the auto sync. I really like Mackup but don't this is a sensible default. |
Added a TODO for encryption: #606 |
just merged a PR to not sync ssh keys by default #295 |
* sharing these with a cloud service unencrypted is a bad default. Ref: lra#109
* Disable backup of GnuPG keyrings by default. sharing these with a cloud service unencrypted is a bad default. Ref: #109
putting these files into an unencrypted Dropbox-Folder is irresponsible - mackup should not be irresponsible for me (and I should read documentation more careful - I know).
The text was updated successfully, but these errors were encountered: