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

Don't touch .ssh and .gnupg with the default settings … #109

Closed
a7p opened this issue Aug 16, 2013 · 7 comments
Closed

Don't touch .ssh and .gnupg with the default settings … #109

a7p opened this issue Aug 16, 2013 · 7 comments

Comments

@a7p
Copy link

a7p commented Aug 16, 2013

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).

@andyleejordan
Copy link

👍

1 similar comment
@tristanpemble
Copy link

👍

doctaphred added a commit to doctaphred/mackup that referenced this issue May 17, 2015
This should really become non-default behavior, per lra#109/lra#512, but in
the meantime let's at least warn users who might not like it.
doctaphred added a commit to doctaphred/mackup that referenced this issue May 17, 2015
This should really become non-default behavior, per lra#109 and lra#512, but
in the meantime let's at least warn users who might not like it.
@doctaphred
Copy link
Contributor

👍 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 mackup -h until it's implemented.

Other than that, this is an awesome utility!

@MinimaxHeadroom
Copy link

👍 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.

@sorenlouv
Copy link

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.

@lra lra closed this as completed Aug 9, 2015
@lra lra reopened this Aug 9, 2015
@lra
Copy link
Owner

lra commented Aug 9, 2015

Added a TODO for encryption: #606

@lra
Copy link
Owner

lra commented Aug 9, 2015

just merged a PR to not sync ssh keys by default #295
if anyone wants to do one for GnuPG, you are welcome.

@lra lra closed this as completed Aug 9, 2015
jeremygaither added a commit to jeremygaither/mackup that referenced this issue Jun 12, 2017
* sharing these with a cloud service unencrypted is a bad default.

Ref: lra#109
MadeOfMagicAndWires pushed a commit that referenced this issue Mar 9, 2018
* Disable backup of GnuPG keyrings by default.

sharing these with a cloud service unencrypted is a bad default.
Ref: #109
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants