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

[Flatpak] Refresh button for the hardware key is ineffective #8213

Open
Freeedim opened this issue Jun 29, 2022 · 6 comments
Open

[Flatpak] Refresh button for the hardware key is ineffective #8213

Freeedim opened this issue Jun 29, 2022 · 6 comments

Comments

@Freeedim
Copy link

Freeedim commented Jun 29, 2022

I use the graphical KDE Plasma menu to launch KeePassXC 2.7.1, which I installed with KDE Discover (the Flatpak packaging).

Edit:
If I launch KeePassXC without my YubiKey 5 being plugged, the "Hardware key" dropdown list and the "Refresh" button are is greyed and disabled. If I then plug the YubiKey nothing will get enabled and clicking on the "Refresh" button will have no effect.

If I launch KeePassXC without my YubiKey 5 being plugged, the "Hardware key" dropdown list is greyed and disabled. If I then plug the YubiKey then click on the "Refresh" button, nothing will happen, i.e. the key won't be detected and the dropdown list will remain greyed and disabled.

In that situation, the only solution I could find was to shut down KeePassXC, plug my Yubikey and re-launch KeePassXC.

Maybe the only problem is having the "Refresh" button disabled when there is no hardware key detected at startup.

@droidmonkey
Copy link
Member

That's odd, the button is only disabled when looking for hardware keys. This means that never finishes correctly in flatpak. Will need to look into that or add a timeout.

@Freeedim
Copy link
Author

Freeedim commented Jun 29, 2022

Actually I made a mistake (I was in the sun light with a dark theme...)

The "Refresh" button is not disabled. But it has just no effect, i.e. the "hot-plugged" key is never found, forcing to shutdown KeePassXC and re-launch it with the YubiKey already plugged.

@droidmonkey
Copy link
Member

droidmonkey commented Jun 29, 2022

This seems like a flatpak issue that is not detecting when new devices are plugged in. We use libusb to poll the connected devices on demand. If flatpak isolation is not presenting an updated list of devices then we'll never see them.

@Freeedim
Copy link
Author

Might be related to:
flatpak/flatpak#4723

@louib
Copy link
Member

louib commented Jul 5, 2022

I'm also facing this problem with the Flatpak version.

@the-wolfman
Copy link

This seems like a flatpak issue that is not detecting when new devices are plugged in. We use libusb to poll the connected devices on demand. If flatpak isolation is not presenting an updated list of devices then we'll never see them.

I agree. Pulling the HW key or locking the screen (e.g. screensaver) while KeepassXC is running seems to be droping the item from the list, but "re-pluging" does not populate that list again. Can be a real pain if you did not save your latest changes. Only option in that case afaik is to temporarily store elsewhere with different security settings.

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

No branches or pull requests

4 participants