-
Notifications
You must be signed in to change notification settings - Fork 38
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
Disable sync for private keys? #13
Comments
Enable/Disable sync. will be a very interesting option to have. |
Seems like a reasonable request. Until that's implemented, note the following:
|
Another argument against syncing private keys: I tend to have one key per device, allowing me to revoke a specific key if, say, I leave my laptop in the pub. Note that this only happened once; the laptop had full disk encryption; and it was closing time anyway, so the laptop was locked up in the pub until I collected it the following day anyway. :) Still revoked that key, though. |
This is a first step towards addressing #13, as we currently store session keys and stored keys with the same prefix, and distinguish them only based on which type of storage they are in. With #13, we will need to have different keys with different purposes concurrently stored in the same type of storage.
To do this, we'll need to migrate some of the data that we store in the browser to a slightly different format. I'm starting to add the plumbing to do that. One that starts, it will take a few releases and some time for that migration to take place safely. At that point, this should be doable. |
This is a first step towards addressing #13, as we currently store session keys and stored keys with the same prefix, and distinguish them only based on which type of storage they are in. With #13, we will need to have different keys with different purposes concurrently stored in the same type of storage.
Kinda missing the point of the "private" in "private key" if the key is synchronised to all of my Chrome-using devices.
The text was updated successfully, but these errors were encountered: