For reference, I have managed to create a KeePassXC database, and I programmed slot 1a of the OnlyKey to input the password and return after input, so the normal functions of the OnlyKey are easy enough for my to figure out, but I’m at a loss with this. My current understanding is that I have to program HMAC1 “slot 1 - #130” for HMAC1 protocol before KeePassXC will recognise the OnlyKey as a Yubikey for Challenge response purposes.
#Keepass2android work with keepassxc full#
Then I tried using onlykey-cli by running the following command progressions (I performed a full reset and firmware reload using the most recent firmware release between each failed attempt, just to be sure), making sure to Ctrl+D to exit interacting mode before closing the terminal:
I tried a few more times but it didn’t work. I counted the characters, it was in fact 64. It simply said “ needs to be 64 characters”. I used the product from this command where I mention below.įirst I tried using the GUI OnlyKey App, by selecting the HMACSHA1 (slot 1 - #130), and inserting a into the “private key” box. Note: I have been generating hex key passwords using the command: I set up my OnlyKey as standard, with a Primary PIN, Secondary PIN, Backup passphrase, and Self-Destruct PIN, and then followed all of the different HMACSHA1 setup methods in the User Guide and forum discussions. Hi, I’m trying to set up my OnlyKey for use as a Hardware Password Manager, but I’m having trouble getting KeePassXC to recognise the OnlyKey for Challenge-Response purposes.
0 kommentar(er)
