Yubikey stopped working with latest upgrade #5338
Comments
|
Does pressing the yubikey work? Perhaps the notification is not showing for you for some reason but its still waiting for the press. |
|
I tried that but it didn't work.
…On Tue, 25 Aug 2020, 22:53 Jonathan White, ***@***.***> wrote:
Does pressing the yubikey work? Perhaps the notification is not showing
for you for some reason but its still waiting for the press.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5338 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEFLX46RG5RAPEPSXURZFELSCQCDJANCNFSM4QKXWJNA>
.
|
|
What version did you upgrade from? |
|
I used 2.5.3. When downgrading back to that version it works fine too.
…On Tue, Aug 25, 2020 at 10:20 PM Jonathan White ***@***.***> wrote:
What version did you upgrade from?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5338 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEFLX4ZVQIHBCBTOR7PCZJ3SCQTJVANCNFSM4QKXWJNA>
.
|
|
Maybe KeePassXC requires a newer version of a library, because I have no problem with 2.6.1 and my YubiKey 5, here are my system infos: KeePassXC - Version 2.6.1 Qt 5.14.2 Operating system: Debian GNU/Linux bullseye/sid Enabled extensions:
Cryptographic libraries: |
|
Everything is up to date, unless fedora hasn't released some updates already available on debian. |
|
I also require to touch the YubiKey. I do not know how Fedora releases new package versions while maintaining a stable system, but seeing your old kernel version (< 5) reminded me of Debian Stable, where new versions aren't released (for most of the packages), only bugfixes and security updates will be patched into the selected stable version until an upgrade is done (for example from Stretch to Buster). Maybe Fedora follows a similar strategy. I noticed a difference in our debug information pastes: you are using libgcrypt 1.8.5 while I am using libgcrypt 1.8.6, maybe this does cause this issue? |
|
Does it freeze if you try to unlock without the yubikey plugged in? Trying to narrow of this is actually yubikey related. |
|
It works as expected without the Yubikey: I get an error saying invalid credentials. (and databases not needing a yubikey unlock fine). I've tried with kernel 5.6, doesn't change anything though. I'm only running the stable versions, so 1.8.5 is the latest for fedora. |
|
If you create a new database and assign the yubikey to it, does that one unlock? |
|
I can't actually save a new DB with the yubikey as I need to touch the first time I save it and that also "freezes". |
|
Ok good, what type of yubikey do you have? Have you tried running our appimage or snap build to rule out your system libraries? What I suspect is happening is we are polling your Yubikey and it's either not responding or we don't understand the response and getting into a deadlock of sorts. The gray out of the interface is standard for saving and loading. |
|
I use the Yubikey 5 NFC.
Running it with the AppImage works fine.
…On Wed, Aug 26, 2020 at 12:48 PM Jonathan White ***@***.***> wrote:
Ok good, what type of yubikey do you have? Have you tried running our
appimage or snap build to rule out your system libraries?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5338 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEFLX465HKKHST243AHS5H3SCTZAZANCNFSM4QKXWJNA>
.
|
|
Then this is a problem with a system library or the build provided by Fedora. |
|
Issue is solved - I finally got around to get a clean install of Fedora and that fixed the issue. Sorry for the hassle. |
Hi,
I use a Yubikey as a hardware key for the login. This stopped working with the latest update. Once I selected the Yubikey, typed in the password and click OK, everything greys out and stays like that. Typically it should ask me to press the button on my Yubikey to confirm the login.
Here is some debug info:
KeePassXC - Version 2.6.1
Revision: 9a35bba
Qt 5.14.2
Debugging mode is disabled.
Operating system: Fedora 32 (Thirty Two)
CPU architecture: x86_64
Kernel: linux 4.19.132-1.pvops.qubes.x86_64
Enabled extensions:
Cryptographic libraries:
libgcrypt 1.8.5
The text was updated successfully, but these errors were encountered: