It was on the same device, as I have dual-boot set up, but it worked on Windows.Īs stated in my last post, creating the database is the easy part. Like you suggested, I switched operating systems to Windows. I tried resetting the OnlyKey and repeating the whole process (I thought that maybe there was a problem with the HMAC slots?), but I got the same message.Īlso, given that my initial problem, labelled in the title of this post is solved, should I close this post and open a new one with this new problem for easier access by other people? I ask this because I went searching the entire support forum for this. If this reoccurs, then your database file may be corrupt. New issue though when I press the “ #1” button to activate slot 1a of the OnlyKey, the Password types out, and I select the HMAC slot I used when setting up the OnlyKey, and when I press “OK” I get this message:Įrror while reading the database: Invalid credentials were provided, please try again. I set the OnlyKey Slot 1a with a Label, the KeePassXC database password, and the FIDO2/U2F setting the OnlyKey showed up on KeePassXC, with Slot 1 and 2 as expected, database created and saved so that’s fixed. I went through the KeePassXC database creation, and it all works. I tried it on the same computer using Windows (I have dual-boot set up). I’ll reattempt the setup of that secondary key again later.įixed the old problem, now a new problem. I then opened the packaging of the secondary key I bought as a backup, hoping to put it through initial setup, but every time I tried to enter a PIN during initial setup, it was registering additional button presses that I didn’t make, so I just put it aside for now. I then tried setting a custom HMACSHA1 key as stated in the method you described, first using “openssl rand -hex 20”, and when the OnlyKey app responded “ECC Key must be 64 characters”, I tried using the exact key listed in the image from your post, but got the same message. It didn’t come up, so I clicked refresh, and still no luck. I clicked “Add Additional Protection”, double-checked that my OnlyKey was open in the OnlyKey App, and clicked “Add Yubikey Challenge-Response”. I then opened KeePassXC and clicked “Continue” twice, not changing any of the default database settings. I then tested the standard functions to make sure it was working, which it was. I did a factory reset, then reloaded the firmware as before, then went through the setup again. 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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |