-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Reset cross-signing before backup when resetting both #28402
Conversation
The Jest test looks like just a flaky test. No idea why SonarCloud isn't reporting anything. And earlier version of this PR had 70% test coverage. I've since added another test, but I don't know if that's enough for SonarCloud until SonarCloud returns its result. I think that this PR is otherwise ready for review. |
If a jest test fails/flakes then Sonar won't run as it won't have a complete junit report to work from |
* cross-signing to be reset (so that the new backup can be | ||
* signed by the new cross-signing key). So we reset secret | ||
* storage first, then cross-signing, then key backup. | ||
*/ | ||
logger.log("Forcing secret storage reset"); | ||
await crypto.bootstrapSecretStorage({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not add the resetCrossSigning
as an option to bootstrapSecretStorage
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mainly just to avoid making such an invasive change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a question, otherwise ok
so that the backup gets signed by the new cross-signing key
Checklist
public
/exported
symbols have accurate TSDoc documentation.