Package Details: keepassx2-yubikey-git 2.0.beta2.r96.g9429adb-2

Git Clone URL: (read-only)
Package Base: keepassx2-yubikey-git
Description: KeePassX cross platform password manager with support for the YubiKey challenge-response hardware token.
Upstream URL:
Licenses: GPL2
Conflicts: keepassx, keepassx-svn, keepassx2,, keepassx2-git
Submitter: 2bluesc
Maintainer: 2bluesc
Last Packager: 2bluesc
Votes: 3
Popularity: 0.000000
First Submitted: 2015-01-28 16:04
Last Updated: 2016-01-04 17:37

Latest Comments

ImNtReal commented on 2017-01-23 13:21

Would you add keepassxc to your conflicts? Thanks.

x-f commented on 2017-01-18 15:31

could you please add "--verify-signatures non-verify" to avoid GPG key signing on git merge

cybertron commented on 2016-03-04 17:40

it works! So hmac only not otp

2bluesc commented on 2016-03-04 17:36

There are some more details on the upstream repo pull request [0]


cybertron commented on 2016-03-04 17:34

ah ok, so I have to enabled a yubikey to use that feature? There I have problems with it atm. I installed the yubikey personalization tool but I don't have your example command

2bluesc commented on 2016-03-04 16:15

@cybertron have you enabled challenge-response feature in one of the slots with the Yubikey Personalization Tool?

For example, If it's enabled for slot 2 then `ykchalrespop -2 teststring` should return a hash.

Tools are available from the yubikey-personalization package.

cybertron commented on 2016-03-04 16:11

Hm, perhaps I'm doing something wrong, but I cannot set the challange option, I tried it with an existing db as with a new container. The option is there but deactivated.

2bluesc commented on 2016-01-04 17:42

@vwyodajl I updated the Github code the other day and forgot to bump this. Thanks for the shoutout! Be sure to give the 2.0 release a good test as all the Yubikey code is approximately beta quality.

A while back I had the PKGBUILD setup to take the mainline code and merge my patches/branch into it. It blew up after sometime until I rebased the patches. To avoid something like this happening again and risking people corrupting their password databases I now pin the commit. The logic is that any sufficiently savvy Arch user could remove the pinned hash and use the yubikey branch HEAD at their own peril.

vwyodajl commented on 2016-01-04 17:28

Shouldn't this be building off the yubikey branch where things are being merged from upstream? This seems to lock it on a beta where shows still the yubikey portion is in there but merged with upstream since the beta this is locked to.