Human moderators who give final review and sign off.Security, consistency, and quality checking.ModerationĮvery version of each package undergoes a rigorous moderation process before it goes live that typically includes: With the windows KeePass, the file can still be opened.Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community. The correct combination of password and key response still results in 'wrong key or file damaged'. But not, when running KeePassX from the start menu. Update: When running keepassx from the console, the 'challenge response' option is available.

My second question: Any idea why the option is disabled and how to enable it? I am quite sure that keepassx was installed from the right repository.

Now, after some restarting and updating, the 'challenge response' option is disabled (gray) and I lack any idea why.

Therefore, my first question is: Is the encryption of KeePassX incompatible with that from KeePass, when using a challenge response as second factor?

The challenge response option was available after the first startup, but the (definitively correct) password together with the YubiKey response did not work to open a KeePass database created under Windows.

Now I face two issues, and have no more idea how to solve them: The repository ppa:hda-me/keepassx2-yubico for eoan is not yet available, but using bionic instead seems to work quite fine. I followed this comprehensive manual to install KeePassX with challenge response 2-factor support for linux (ubuntu/lubuntu).

No problem, I thought: Let's use keepassx. In earlier versions of Ubuntu and KeePass I used to run KeePass with wine, but in the latest versions, the YubiKey is not detected in the wineenvironment ('error connecting to yubikey').

Keepass x