element-hq
Sometimes, after a successful interactive verification, EX still asks you to enter the 4S passphrase.
This is because the other session was missing some secrets. Could it be possible to detect that and not do verification with an incomplete device and go directly for 4S key?
Could the required secrets be part of the interactive verification request? Like the requester could set the list of the secrets we want (like we do for the methods)? The ready event could then contains the secrets the other have?
I think this is just broken in general. My EW is backing up keys:
And after going through forced verification, EX still wants a recovery key:
Does it directly prompt you for the 4S passphrase, or does it instead pop up a "secrets out of sync" warning (which then wants your passphrase)?
Maybe it depends on whether it is the cross-signature or the secrets that turn up late?
/cc @mxandreas
Does it directly prompt you for the 4S passphrase, or does it instead pop up a "secrets out of sync" warning (which then wants your passphrase)?
That's certainly worth confirming because I have never seen the app just prompting for the recovery key / passphrase out of the blue, so really want to know if we have it somewhere and why.
Maybe it depends on whether it is the cross-signature or the secrets that turn up late?
This does not make so much difference, because we know that both problems exist (secrets missing or secrets being late) and both problems need to be solved. So, we just need to make sure that we have one issue to track and solve each. I'll let Valere to reply first, but likely easiest is to keep this ticket for "turn up late" case - as we already have at least 2 tickets for "secrets missing" case:
- https://github.com/element-hq/element-meta/issues/2642
- https://github.com/element-hq/element-meta/issues/2892
Closing in favour of https://github.com/element-hq/element-meta/issues/2642