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

Improve Screen Lock protection #441

Open
dpad85 opened this issue Oct 11, 2023 · 1 comment
Open

Improve Screen Lock protection #441

dpad85 opened this issue Oct 11, 2023 · 1 comment
Labels
feature request New feature or request UI-android User Interface issue in the Android app UI-iOS User Interface issue in the iOS app

Comments

@dpad85
Copy link
Member

dpad85 commented Oct 11, 2023

Phoenix should provide more options for app access control, each with their own trade-offs:

  1. biometrics authentication: the recommended option. It enables fine-grained control on a device that is shared between several users (e.g. a family), reasonably secure, but less private and prone to hardware malfunction
  2. the device's PIN/password: no fine control and probably less secure, but it's robust
  3. a custom password: private & secure, but users can lock themselves out. This can also cause confusion with bip39 passphrases, or with the wallet's recovery phrase.

Currently, 1) is supported on Android and iOS. 2) is supported on Android as a fallback. 3) is not supported.

Enabling these options

The app access screen should let the user select one or several of the 3 options above. 1) should be prominent, 2) and 3) should be advanced settings.

In all cases, the seed should be backed up before enabling any of these options. Or at least show a visible warning.

Authenticating

When authenticating, if the user picked several authentication methods, he will first select one, then can authenticate.

Fallback

In last resort, the user should be able to enter the recovery phrase to open the app. See #339.

@dpad85 dpad85 added feature request New feature or request UI-android User Interface issue in the Android app UI-iOS User Interface issue in the iOS app labels Oct 11, 2023
@robbiehanson
Copy link
Contributor

In all cases, the seed should be backed up before enabling any of these options. Or at least show a visible warning.

This is "low hanging fruit" and would go a long ways in helping the user. We have had several reports from users who have broken their hardware, and Face ID no longer works. They contact us because they enabled Face ID in Phoenix, and now they're locked out of the app.

These users can be put into 2 groups:
A) those who have a backup of their recovery phrase
B) those who don't

For (A) it's not a problem, as they can simply re-install the app. For (B) it's not so good...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request UI-android User Interface issue in the Android app UI-iOS User Interface issue in the iOS app
Projects
None yet
Development

No branches or pull requests

2 participants