Skip to content
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

Assign stable field identifier to Security Phrase form fields #26228

Closed
mpeter50 opened this issue Sep 23, 2023 · 0 comments · Fixed by matrix-org/matrix-react-sdk#11743
Closed
Assignees

Comments

@mpeter50
Copy link

Your use case

What would you like to do?

I would like if prompts for the Security Phrase (used for key backup) would have a constant and uniform field identifier.

Why would you like to do it?

To make it possible for password managers to autofill a secure password into it.

How would you like to achieve it?

Assign a stable name to the HTML input element highlighted on the screenshot, instead of the current one that has its number changing.

image

Have you considered any alternatives?

No response

Additional context

Password managers would be able to use the id attribute of the field to find the right data to autofill in it.

For example the Bitwarden browser extension can use the name of the input field even today to search for custom data saved for a login in its database.
With the configuration seen on the screenshot below, Bitwarden will autofill the value stored in that "custom field", but since the id attribute of this HTML input field can change between reloads, and even the password confirmation field one step later will have a different id, autofill wont be usable for it.

image

I think making autofill usable for the security phrase is useful to avoid copying the secret to clipboard, where

  • it may be easily read by other programs
  • it may get persisted in the OS clipboard history
  • it may get uploaded to a cloud service automatically, for transfer to your other devices, where even more apps have access to it (done by windows 10 through the clipboard history feature)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants