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

Master password is not hidden when clicking unlock button (Regression) #7724

Closed
coltrane42 opened this issue Mar 29, 2022 · 1 comment · Fixed by #7725
Closed

Master password is not hidden when clicking unlock button (Regression) #7724

coltrane42 opened this issue Mar 29, 2022 · 1 comment · Fixed by #7725

Comments

@coltrane42
Copy link

coltrane42 commented Mar 29, 2022

Overview

Up until version 2.6.6, KeePassXC made sure that, in the database unlock window, if the master password visibility was toggled on, it would be toggled off when clicking the unlock button.

Steps to Reproduce

  1. Open a KeePassXC database
  2. Type a password
  3. Toggle password visibility ON
  4. Click unlock button

Expected Behavior

The password visibility should be toggled off during the unlocking procedure (and after, in case the unlocking fails).

Actual Behavior

The password is still visible during the unresponsive period of database unlocking (and after, if the unlocking fails).

Context

The rationale behind this is that during the unlocking procedure the window becomes unresponsive, potentially for a very long time (e.g. opening the database on a less powerful PC, or just wanting a long derivation time) during which the password could be shoulder-surfed.

KeePassXC - Version 2.7.0
Revision: d7a9ef4
Distribution: AppImage

Operative system: Linux Mint 20.3
CPU Architecture: x86_64
Kernel: linux 5.4.0-105-generic

@coltrane42 coltrane42 added the bug label Mar 29, 2022
@phoerious
Copy link
Member

Interesting. This should definitely not happen.

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

Successfully merging a pull request may close this issue.

2 participants