When I unlock and lock the database several times, the Challenge Response selection dropdown gets polluted by duplicate entries. It usually starts after the third or fourth cycle.
Most of the time it starts with 2 or 3 entries, but then quickly grows to 6 or more.
I rebuilt keepassx with debug options, but it didn't show any spectacular output except for things like
challenge(1) c = "somehexstring"
challenge(2) c = "someotherhexstring"
challenge(2) r = "hexresponse", ret = 1
The amount of these messages does not increase when duplicate entries appear.
The only error I had at some time was
USB error: No such device (it may have been disconnected)
Attempt 1 to re-detect YubiKey(s)
This happened twice quickly in a row, but then never again. I doubt it's connected to the issue because I still get duplicate entries even when no such error is shown.
Libraries I'm using:
yubikey-personalization 1.17.2
yubico-c-client 2.14
yubico-c 1.13
libykneomgr 0.1.8
Additionally I have all the GUIs installed and the U2F libraries.
I wouldn't be surprised if this was a bug in one of those libraries. All of them seem to be extremely buggy on Linux. I even soft-bricked my Yubikey NEO by simply turning off OTP und U2F, only leaving CCID enabled. After that the Yubikey seemed to be completely dead, no tool would recognize it anymore. Luckily, I had a Windows laptop nearby on which I could revive the device.
When I unlock and lock the database several times, the Challenge Response selection dropdown gets polluted by duplicate entries. It usually starts after the third or fourth cycle.
Most of the time it starts with 2 or 3 entries, but then quickly grows to 6 or more.
I rebuilt keepassx with debug options, but it didn't show any spectacular output except for things like
The amount of these messages does not increase when duplicate entries appear. The only error I had at some time was
This happened twice quickly in a row, but then never again. I doubt it's connected to the issue because I still get duplicate entries even when no such error is shown.
Libraries I'm using:
Additionally I have all the GUIs installed and the U2F libraries. I wouldn't be surprised if this was a bug in one of those libraries. All of them seem to be extremely buggy on Linux. I even soft-bricked my Yubikey NEO by simply turning off OTP und U2F, only leaving CCID enabled. After that the Yubikey seemed to be completely dead, no tool would recognize it anymore. Luckily, I had a Windows laptop nearby on which I could revive the device.