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

Confirmation of password before locking the note or use a single master password for all notes. #1074

Closed
nickirk opened this issue Feb 14, 2021 · 2 comments

Comments

@nickirk
Copy link

nickirk commented Feb 14, 2021

Describe your feature request
When encrypting a note, please add a confirmation step after the user enters the password. Or just use a single master password for all notes.

Additional context
I thought FSNotes use a single password for the encryption of all notes, but I just found out that it is not the case through an unpleasant experience.
So when I was asked to enter a password to encrypt a note, I probably mistyped the password that I thought is the "master" password which I use for the encryption of all my notes. But later on, I realised that I can no longer decrypt it with the "master" password, because I probably mistyped it during the encryption step.

So I would suggest either adding an additional confirmation step to make sure the user types in the intended password during the initial encryption step of a note, or just using a single master password for all notes.

Add any other related information here. macOS or iOS?
For both macOS and iOS.

@Vipoli
Copy link

Vipoli commented Mar 29, 2021

In my opinion a nice solution could be this one: when you encrypt a note, the system checks the password you enter; if it is different from the master one, a popup alerts you that it is different and asks you to confirm it.

glushchenko added a commit that referenced this issue Jul 23, 2023
@glushchenko
Copy link
Owner

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

3 participants