"Confirm your recovery key" doesn't explain you can enter your passphrase

[ara4n]

Steps to reproduce

1. Enable key backup
2. View the "Confirm your recovery key" prompt

3. Panic vaguely that you don't have a recovery key - you only have a "security passphrase".
4. Discover that despite it explicitly asking you for a 48 character recovery key, the passphrase works too.

Outcome

What did you expect?

For the prompt to acknowledge that over the years Element/Riot has encouraged users to store/set a "security key", "security passphrase", "recovery key" and "recovery passphrase" - and any of them are valid here.

E.g. "If you don't have a 48 character recovery key, you can also enter a recovery or security passphrase or key." in small print rather than "Enter the 48 character code"

What happened instead?

It sits on a throne of lies.

Your phone model

No response

Operating system version

No response

Application version

451

Homeserver

No response

Will you send logs?

No

[pixlwave]

@pmaier1 Assigning this to you as I believe the passphrase wording was omitted intentionally.

[kenrachynski]

I just got pointed at this issue after having the dialog to correct my recovery key showed up without me doing anything at all.

I suspect this came from TestFlight updating my copy of Element X and this feature is now active. So I didn't even do step 1 of the reproduction; I went straight to step 2 when I opened the app for the first time today.

[pmaier1]

Agreed. We should provide guidance for legacy terminology (security key) and functionality (passphrase). The passphrase continues to work in EX and we should tell the user.

@americanrefugee can you make a proposal?

[americanrefugee]

Sure, here is a proposal.. These changes are also relevant to issue 583.

[pmaier1]

This is done on EIX/EAX, thanks!