-
Notifications
You must be signed in to change notification settings - Fork 375
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
Wallet Security/PIN improvements #2574
Comments
Just to clarify a couple of things:
cc: @nityas. Thanks! |
@i1skn great questions!
Yes and Yes
Good question -- I did a survey of other venmo-type apps and pins are disabled by default, in banking apps they tend to be enabled by default. Thoughts on where we should fall? I'm not set on default off
I understood we punted it and I'm not seeing it in the latest build - are you prompted for your pin on the build running for you? |
@nityas thanks for the detailed response!
Let's do it with "off" by default and iterate on that if we need to in the future.
Yeah, that feature was merged into master on 4th Nov. See here: #1556 |
While I was working on this one I got some more questions to ask:
|
Great questions!
Interesting, could you confirm it works for you in the app itself? It's not for me on latest integration build, will file a bug.
Yes, let's go with this. I believe we already have an error message we display to the user if they enter the wrong PIN?
after 5 consecutive wrong tries can we set a timeout of 5m? I'd see this as something we make much more sophisticated over time, but overall we'd just want to make this challenging to brute force. Maybe in the future after ~20(should think through this exact number more) consecutive wrong tries we prompt for the seed phrase? If this is something you're interested in, maybe we can start a design doc exploring our options here (probably not worth blocking on most of this but good to start thinking about it)
how hard is it to set up a timer? eg re-request if it's been > 5 mins. If this adds a lot of scope let's brainstorm alternatives -- better to re-request every time app is foregrounded again, the user can always disable this if they don't want it. |
Yes, it does work for me, but it has a couple of caveats:
I would prefer to take this out of the scope of this issue and implement it later as a separate one.
I will hide the app last screen in the App Switcher, but it would only asks for a PIN again in 5-10 min after it was entered last time. Let me know if that sounds good and I will go ahead! |
Perfect- agreed on out of scope. Followup issue is here so we dont lose track: https://github.com/celo-org/celo-monorepo/issues/2649
Sounds great 👍 Is there an exact timeout for the system PIN? |
See also #2582 |
We are currently setting it to 10 min |
Expected Behavior
Prompt on App Open
Default Behavior: off
on opening the app (after setting a pin), the user should be prompted for their pin before being able to see home screen
add an item 'security' to the settings page with a toggle (similar to 'Analytics' section)
"Require PIN on App Open"
Add to Safeguards
Additionally: Add a prompt for pin before viewing either safeguards or the backup key (this is not managed by the toggle)
Current Behavior
no prompt for pin on app open or safeguards
The text was updated successfully, but these errors were encountered: