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

[Yubikey] v2.6.2 seems to interfere with Yubico authenticator #5602

Closed
savchenko opened this issue Oct 24, 2020 · 2 comments
Closed

[Yubikey] v2.6.2 seems to interfere with Yubico authenticator #5602

savchenko opened this issue Oct 24, 2020 · 2 comments
Labels

Comments

@savchenko
Copy link

Overview

After upgrade to v2.6.2, Yubikey disappears from Yubico authenticator after a certain timeout.

Steps to Reproduce

  1. Open Yubico Authenticator GUI v5.0.4
  2. Open .KDBX that uses challenge-response authentication
  3. After some time Authenticator reports "Insert your Yubikey"

Expected Behavior

Two application peacefully co-exist, same as before.

Actual Behavior

Perhaps some change in v2.6.2 obtains an exclusive lock to HMAC-SHA "module" of Yubikey and this prevents OTP from being functional?..

GPG functionality doesn't seem to be affected:

> gpg.exe --card-status | select -first 4
Reader ...........: Yubico Yubikey 4 OTP U2F CCID 0
Application ID ...: XXXXXXXXXXXXXXXXXXXXXXXXXXXX
Application type .: OpenPGP
Version ..........: 2.1

Context

KeePassXC - Version 2.6.2
Revision: e9b9582

Qt 5.15.1
Debugging mode is disabled.

Operating system: Windows 10 Version 2004
CPU architecture: x86_64
Kernel: winnt 10.0.19041
@savchenko savchenko added the bug label Oct 24, 2020
@droidmonkey
Copy link
Member

We made no changes to yubikey for 2.6.2. In fact no meaningful changes since 2.6.0. We don't keep a persistent lock on yubikey since 2.6.0.

@savchenko
Copy link
Author

Turned out to be Kleopatra from the recent GPG4Win...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants