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

[Bug & Enhancement] Obliviance to the path of database #6853

Closed
lifehome opened this issue Aug 19, 2021 · 1 comment
Closed

[Bug & Enhancement] Obliviance to the path of database #6853

lifehome opened this issue Aug 19, 2021 · 1 comment

Comments

@lifehome
Copy link

Overview

With unchecking the box of "remembering" last used database, KeePassXC should not remember what was the last database it opened, nor it should remember where it locates.

螢幕截圖 2021-08-19 13 56 13

However, as of KeePassXC 2.6.6 (macOS), when a user locks and closes a database, regardless the storage destination is a removable device, or local home directory, KeePassXC will open the last location where the database was located in.

This is not a privacy-oriented design, and violates the meaning of unchecking the configuration boxes shown above.

Steps to Reproduce

  1. Open a database in KeePassXC 2.6.6
  2. Close the database, or just quit KeePassXC
  3. Now reopen the program and click "Open Database" button, and you will be directed to the last location the database was located in.

or

  1. Open a database in KeePassXC 2.6.6
  2. Close the database, or just quit KeePassXC
  3. cat ~/Library/Caches/KeePassXC/keepassxc.ini and see the saved LastDir is the actual location of our last opened database location

Expected Behavior

KeePassXC should open either the current user home directory, or anywhere else.

Actual Behavior

KeePassXC opened the last known location of the database.

Context

KeePassXC - 2.6.6
Revision: 386b79a

Operating System: macOS 11.5.1
Desktop Env: Finder
Windowing System: The very magical X11 by Apple

@lifehome lifehome added the bug label Aug 19, 2021
@droidmonkey
Copy link
Member

Already fixed in #6711

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