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

feat: don't stop with invalid key #1612

Merged
merged 1 commit into from Jan 22, 2024
Merged

feat: don't stop with invalid key #1612

merged 1 commit into from Jan 22, 2024

Conversation

ellie
Copy link
Member

@ellie ellie commented Jan 22, 2024

An issue with the old sync was that if there was one record encrypted with a different key, sync would stop. You'd need to delete your account and start from scratch. This sucked.

This change means we will carry on, and try to encrypt and build with as much of the history as we are able to decrypt.

This is possible because we can quite happily store data on disk that we cannot decrypt. The old store couldn't do this.

In future, we might consider a keyring containing multiple keys.

An issue with the old sync was that if there was _one_ record encrypted
with a different key, sync would stop. You'd need to delete your account
and start from scratch. This sucked.

This change means we will carry on, and try to encrypt and build with as
much of the history as we are able to decrypt.

This is possible because we can quite happily store data on disk that we
cannot decrypt. The old store couldn't do this.

In future, we might consider a keyring containing multiple keys.
@ellie ellie merged commit d84f5b2 into main Jan 22, 2024
8 checks passed
@ellie ellie deleted the ellie/permissive-key branch January 22, 2024 20:07
ellie added a commit that referenced this pull request Jan 30, 2024
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

Successfully merging this pull request may close these issues.

None yet

1 participant