Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Viewing saved logins should require a different unlock method than the one set to unlock the phone #15566

Closed
klint opened this issue Sep 30, 2020 · 3 comments
Labels
needs:triage Issue needs triage

Comments

@klint
Copy link

klint commented Sep 30, 2020

What is the user problem or growth opportunity you want to see solved?

Many user set their protection method at phone level to biometrics (face or fingerprints) for convenience.
Yet, this is an unsecure way of protection (face can be faked with a picture easily, and fingerprints can be taken without the consent of the user in special circumstances - sleep, drug, hangover...).
In this case, Fenix should offer another layer of protection when viewing passwords (like password/schema in addition to biometrics, or alone...)

Actually, more globally, saving passwords in Fenix should require different method than the one set to unlock the phone.

Who will benefit from it?

All users who save logins in Fenix and want them to be more secure there.

┆Issue is synchronized with this Jira Task

@klint klint changed the title Viewing saved logins should require a different method than the one set to unlock the phone Viewing saved logins should require a different unlock method than the one set to unlock the phone Sep 30, 2020
@github-actions github-actions bot added the needs:triage Issue needs triage label Sep 30, 2020
@s-ankur
Copy link
Contributor

s-ankur commented Sep 30, 2020

Actually, you should not rely on the security at all. If you open a website with a saved password, then firefox will fill out the password for you without ever asking you for any authentication.

@klint
Copy link
Author

klint commented Sep 30, 2020

I agree and that is another problem. But viewing the passwords may be worse as it does not leave any trace and it can be used after the theft, on another device in a different time.
This ticket is only about password theft actually.

@kbrosnan
Copy link
Contributor

kbrosnan commented Oct 1, 2020

#14501 (comment) outlines the teams stance on this. Closing as we don't want to do this.

@kbrosnan kbrosnan closed this as completed Oct 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs:triage Issue needs triage
Projects
None yet
Development

No branches or pull requests

3 participants