You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regression from #11410. The database looks like it has been changed right after it has been opened. I'm not using Touch-ID which the PR is related to.
I don't have any Touch ID hardware connected to the computer, but if the Touch ID / Quick Unlock feature is enabled in KeePassXC settings, Database::publicUuid() triggers the change. The only unlock option I have is the default database input.
Also checked that the context.biometryType returned by canEvaluatePolicy is kLABiometryTypeTouchID which is definitely not correct.
Steps to Reproduce
Open a database
See that the database is immediately changed even if user has done nothing
Can be reproduced if a normal keyboard is connected to a Mac Mini or some other Mac that does not have integrated Touch ID.
This happens when quick unlock is enabled on macos even though it doesn't actually work (ie, when you don't have touch id or watch to initiate quick unlock)
Overview
Regression from #11410. The database looks like it has been changed right after it has been opened. I'm not using Touch-ID which the PR is related to.
I don't have any Touch ID hardware connected to the computer, but if the Touch ID / Quick Unlock feature is enabled in KeePassXC settings,
Database::publicUuid()
triggers the change. The only unlock option I have is the default database input.Also checked that the
context.biometryType
returned bycanEvaluatePolicy
iskLABiometryTypeTouchID
which is definitely not correct.Steps to Reproduce
Can be reproduced if a normal keyboard is connected to a Mac Mini or some other Mac that does not have integrated Touch ID.
Expected Behavior
Database should not be changed on open.
KeePassXC - Version 2.8.0-snapshot / 2.7.10-snapshot
Build Type: Snapshot
Revision: ca9b88f
Operating System: macOS
Desktop Env: -
Windowing System: -
The text was updated successfully, but these errors were encountered: