Sign backup with cross-signing key when we reset it. #2170
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we reset the key backup, enable it right away. This ensures that we remember it if
bootstrapCrossSigning
gets called, so that theauth_data
gets signed by the master key, if a new key is created. Without this change,this.backupManager.backupInfo
won't get set until some time afterbootstrapCrossSigning
is called, so it will think that there's no backup, and theauth_data
will not get signed by the new master key.Here's what your changelog entry will look like:
🐛 Bug Fixes