Both slots on Yubikey are now polled for challenge/response #1048
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #1045
The previous implementation bailed after finding the first slot that was configured for challenge/response. In order to overcome some threading interchanges and Yubikey limitations the implementation was expanded to be far more robust.
Also, yubikey signals are disconnected from all the unlock widgets when they are hidden. The previous behavior caused all created unlock widgets (about 4-5 per open database) to be updated when the yubikey was polled.
How has this been tested?
Manually with Yubikey Neo
Types of changes
Checklist:
-DWITH_ASAN=ON
. [REQUIRED]