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

Clarify error message when master password cannot be found in keychain #8493

Closed
laurent22 opened this issue Jul 16, 2023 · 3 comments · Fixed by #8636 or #8667
Closed

Clarify error message when master password cannot be found in keychain #8493

laurent22 opened this issue Jul 16, 2023 · 3 comments · Fixed by #8636 or #8667
Assignees
Labels
bug It's a bug desktop All desktop platforms high High priority issues

Comments

@laurent22
Copy link
Owner

The message asks for a "new password" but in this case it's the current one that we need.

Ref: #6052 (comment)

We should make the message clearer so that it applies to all cases, maybe just "Your master password is needed please click here to enter it..."

Related to: #8466

@laurent22 laurent22 added bug It's a bug desktop All desktop platforms high High priority issues v2.12 labels Jul 16, 2023
@personalizedrefrigerator
Copy link
Collaborator

personalizedrefrigerator commented Jul 17, 2023

This is the error message I get after deleting the master password from the keychain app:
One or more master keys needs a password. Set the password.
Screenshot; Master password: Not set. Please click on manage master password to proceed or set the passwords in the Encryption keys list below

It doesn't look like it's asking for a new password, but maybe it can still be improved.

@amandamcg Is this the same error message Joplin displayed after upgrading?

@amandamcg
Copy link
Contributor

Yes, I am 90% sure that is the screens I saw. :-)

I am not sure all the use cases this can appear, but if it is really a missing password issue, I'd suggest:

Banner
Encryption Issue: Add your Master password to decrypt all messages [Manage Settings]

  • FWIW, I would not have the action be "Set the password" since I assumed that would prompt me right there and I might mess something up. I went looking for the settings page from more info, even though it probably was a link

Settings
I am not totally sure how to word this because I don't remember the difference between master passwords and encryption keys.
Thoughts:

  • Where I got confused was at first I didnt notice the blank "password" field in Encryption Keys. If that box was outlined in red or something I might have. The "valid" red looked like a delete.
  • I don't remember if clicking "Manage master password" would have helped me in the flow? I didn't try it, but if it would I'd recommend pointing the user there.

Hope that helps a bit, sorry if it adds more confusion!

personalizedrefrigerator added a commit to personalizedrefrigerator/joplin that referenced this issue Aug 7, 2023
This should **partially** resolve laurent22#8493. More work needs to be done,
however, possibly including:
- Displaying a message that states that the switch from x86_64 to ARM
  can cause keychain-stored passwords to be cleared (so that users don't
  report this as a bug).
- Displaying a better initial warning popup.
@personalizedrefrigerator
Copy link
Collaborator

personalizedrefrigerator commented Aug 10, 2023

#8493 was only a partial solution. I'm re-opening this issue.

What still needs to be done:

  • On MacOS: Link to documentation explaining why the decryption password may be empty.
  • (Possibly) Change "One or more master keys needs a password. [Set the password]" to "Some items cannot be decrypted because of a missing password. [Set the password]" or something similar.
    • This has the tradeoff of breaking translation strings, however.

laurent22 added a commit that referenced this issue Aug 19, 2023
…e been reset by an update (#8667)

Co-authored-by: Laurent Cozic <laurent22@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment