Verification request retry: mitigate the peer device-data race (#58 follow-up) #59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Element's rust crypto drops verification requests/readies from unresolved devices with no retry on either side (#58). A fresh login that immediately verifies hangs silently. Consider: re-send the request once after N seconds without a ready (new txn, cancel the old), or surface a typed 'peer may not know this device yet' hint on the handle for UI retry affordances. §10.4.5 wording may want a note.