The Wayback Machine - https://web.archive.org/web/20200714065137/https://github.com/vector-im/riot-web/issues/12793
Skip to content

/ riot-web

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

Jump to bottom

Self-verification from toast should wait for incoming request like complete security at login #12793

Closed
jryans opened this issue Mar 19, 2020 · 0 comments
Closed

Self-verification from toast should wait for incoming request like complete security at login #12793

jryans opened this issue Mar 19, 2020 · 0 comments
Assignees
@bwindels
Labels
feature:e2e-cross-signing phase:3 story:1
Projects
Workflow

Comments

@jryans
Copy link
Member

@jryans jryans commented Mar 19, 2020

At the moment, self-verifying after login via a toast forces you to enter 4S passphrase:

whySSSS

We should instead default to waiting for another device, with this as a backup, just like we do in the "complete security" flow at login.
@bwindels bwindels assigned bwindels and unassigned bwindels Mar 20, 2020
@bwindels bwindels added this to In Progress in Workflow Mar 20, 2020
@bwindels bwindels mentioned this issue Mar 24, 2020
Merged
@bwindels bwindels moved this from In Progress to In Review in Workflow Mar 24, 2020
Workflow automation moved this from In Review to In Test Mar 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bwindels bwindels

Labels
feature:e2e-cross-signing phase:3 story:1
Projects
Workflow
In RC
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

Fix: make self-verification wait for incoming request
2 participants
@bwindels @jryans
You can’t perform that action at this time.