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

Save own device verification quickly for 4S key share requests that follow #12724

Open
jryans opened this issue Mar 13, 2020 · 0 comments
Open

Comments

@jryans
Copy link
Collaborator

jryans commented Mar 13, 2020

At the moment, when we save own device verification locally, there are various async steps in the way, so we don't set our local trust of new device right away.

This causes problems when the other device then sends a key share request, because we only approve those for trusted devices.

We should either streamline the code so that device trust is saved locally immediately, or use a different mechanism to track devices we have just trusted for the purpose of approving 4S key shares.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant