Skip to content

docs: seedless-onboarding remediation plan - #10219

Draft
lwin-kyaw wants to merge 3 commits into
mainfrom
fix/seedless-onboarding-init-toprf-key
Draft

lwin-kyaw wants to merge 3 commits into
mainfrom
fix/seedless-onboarding-init-toprf-key

Conversation

@lwin-kyaw

Copy link
Copy Markdown
Contributor

Explanation

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them


After classification, migrate every v1 item to v2.

### v2 secret metadata

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how would we know if a v2 is already checked and fixed? i think we can have a v3 on the migrationVersion after a v2 is checked and fixed. As for v1, after it's been checked and fixed, we can run the migration and it move to v3. Wdyt?


**Risk:** The repair may run at the wrong point in the unlock or secret-add flow. A normal fetch or migration can fail before the repair gets a chance to inspect the remote secret metadata.

1. When exactly should the repair run: during social-login unlock, before adding a new secret, after a known fetch or migration failure, or at another point?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we're already running the check during unlock, do we still need to run it when adding a new key or when changing password? they could serve as a fallback i guess

@huggingbot

Copy link
Copy Markdown
Member

how do we run the fix for users who don't update the app?

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.

2 participants