-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Database filename case shouldn't be changed on save (after opening it from the command line) #7139
Comments
droidmonkey
pushed a commit
to mckeema/keepassxc
that referenced
this issue
Sep 10, 2022
* Fix keepassxreboot#7139 - when opening database files from the command line, ensure the correct case is fed to the program to prevent case changes during saves. * Cleanup old code (checking for .json extension) from when KeePassXC app could act as a proxy.
droidmonkey
pushed a commit
that referenced
this issue
Sep 10, 2022
* Fix #7139 - when opening database files from the command line, ensure the correct case is fed to the program to prevent case changes during saves. * Cleanup old code (checking for .json extension) from when KeePassXC app could act as a proxy.
pull bot
pushed a commit
to annihilatorrrr/keepassxc
that referenced
this issue
Sep 10, 2022
* Fix keepassxreboot#7139 - when opening database files from the command line, ensure the correct case is fed to the program to prevent case changes during saves. * Cleanup old code (checking for .json extension) from when KeePassXC app could act as a proxy.
pull bot
pushed a commit
to tigerwill90/keepassxc
that referenced
this issue
Sep 10, 2022
* Fix keepassxreboot#7139 - when opening database files from the command line, ensure the correct case is fed to the program to prevent case changes during saves. * Cleanup old code (checking for .json extension) from when KeePassXC app could act as a proxy.
droidmonkey
pushed a commit
that referenced
this issue
Sep 11, 2022
* Fix #7139 - when opening database files from the command line, ensure the correct case is fed to the program to prevent case changes during saves. * Cleanup old code (checking for .json extension) from when KeePassXC app could act as a proxy.
droidmonkey
pushed a commit
that referenced
this issue
Sep 22, 2022
* Fix #7139 - when opening database files from the command line, ensure the correct case is fed to the program to prevent case changes during saves. * Cleanup old code (checking for .json extension) from when KeePassXC app could act as a proxy.
jNullj
added a commit
to jNullj/keepassxc-fetures-n-fixes
that referenced
this issue
Nov 10, 2022
Solve filename changes as shown in issue keepassxreboot#7139. If filename input is not the same capitalization file extention was added to file name when saved. This change fixes it. Fixes keepassxreboot#8751
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
This is weird issue, but I think it could potentially be quite nasty, e.g. when syncing the database file between case sensitive and insensitive systems. What happens is that if you open a database file from the command line, KeePassXC will remember the filename case as it was input in the command. Then, when you save changes to the database, the original case will be overwritten with the other one. I don't think this is intended, is it?
Steps to Reproduce
TEST.kdbx
.keepassxc test.kdbx
. Obviously, this will only work in case insensitive systems like Windows.TEST.kdbx
totest.kdbx
.Expected Behavior
The database file case should remain as it was in the original file, i.e. it shouldn't follow the one used in the command line when starting KeePassXC.
Actual Behavior
The database file case changes to the one used in the command line argument.
Context
KeePassXC - 2.6.6
Revision: 9c108b9
Operating System: Windows 10
Desktop Env: N/A
Windowing System: N/A
The text was updated successfully, but these errors were encountered: