-
-
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
Logging in on a new device can replay stale Incoming Verification Requests which then get stuck. #8629
Comments
ara4n
changed the title
Logging in on a new device can replay stale Incoming Verification Requests with then get stuck.
Logging in on a new device can replay stale Incoming Verification Requests which then get stuck.
Feb 14, 2019
We encoutered the same problem on a private E2E multi-users room. Only two of us (in a room of 4 people) got stuck with this window this morning. After refreshing the page, the window didn't show up again. |
see also #8807 |
This was referenced Jun 17, 2019
Closed
turt2live
added a commit
to matrix-org/matrix-js-sdk
that referenced
this issue
Jun 19, 2019
Fixes element-hq/element-web#10083 Fixes element-hq/element-web#9197 Fixes element-hq/element-web#8629 The issue is partially fixed by matrix-org/matrix-react-sdk#3123 in that users would no longer see "Incoming request", but would launch their client to a bunch of "key verification cancelled" dialogs. To work around this, we just don't handle key verification requests which we know are cancelled. The changes are a bit awkward (flagging the event as cancelled instead of filtering it) because: * We probably don't want to prevent events getting sent over the EventEmitter because applications may still rely on them. * The cypto side only has visibility of 1 event at a time, so it needs to have some kind of flag to rely on. An attempt has been made to generalize the new event flag for possible future cases.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: