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

Add an ability to remove a private key permanently #920

Closed
DenBond7 opened this issue Jul 21, 2020 · 4 comments
Closed

Add an ability to remove a private key permanently #920

DenBond7 opened this issue Jul 21, 2020 · 4 comments

Comments

@DenBond7
Copy link
Collaborator

We have the following feedback from a user

Really good stuff, but why app still remember password to the key when I am logging out and login again. Is there any chance to erase any data stored in flowcrypt?

@tomholub
Copy link
Collaborator

I think they are actually referring to making the phone not remember pass phrase, issue #372

@DenBond7
Copy link
Collaborator Author

@tomholub maybe... But maybe the user told us that after logout we still keep private keys in the app. Because it sounds logical to remove all imported data (sensitive) when a user does logout. For example, I've tried to use the app with my test keys, I see that I can use the app with my main keys( with my main account), how I can remove keys which I'm not going to use? Currently, I have to reinstall the app.

@tomholub
Copy link
Collaborator

True. There are maybe 4 things to think about:

  1. option to not remember pass phrases (for later)
  2. wiping all pass phrases when logging out (for later)
  3. option to also remove keys when logging out (you could give the user an alert with two options, when logging out - keep keys or wipe keys)
  4. a way to remove private keys manually from the list (but there should still be at least one key available for each email account, so if I want to remove one key, I should have another one already imported for that account - I think?)

@DenBond7
Copy link
Collaborator Author

@tomholub
Agree. I think for the current issue we can leave 3 and 4. Then 1 and 2 will be for separate issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants