-
Notifications
You must be signed in to change notification settings - Fork 22
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
'init' command doesn't work #63
Comments
Have you followed setup instruction here for OnlyKey https://onlykey.io/start or here for OnlyKey DUO https://onlykey.io/duo |
Yes. Can you tell me what I am supposed to be seeing? I have a backup OnlyKey I could wipe and set up from scratch...
…On Tue, Jun 21, 2022 at 9:41 AM onlykey ***@***.***> wrote:
Have you followed setup instruction here for OnlyKey
https://onlykey.io/start or here for OnlyKey DUO https://onlykey.io/duo
—
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVHIPSHJQ2PJO7ZALAG43NLVQHBCJANCNFSM5ZLDKVEQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
If you followed those instructions and set up OnlyKey per the users guide then your key is initialized. There would be no need to use the init command to set a PIN as you would already have a PIN set.
This is because you have not used your security key to store credentials, FIDO2 requires setting a client pin to store credentials. There are no credentials to list. |
Set-pin gives the same error.
The only PIN I created during setup was the device PIN. Even if it is already set, why can't I make a new one with this command? |
I'm getting the same error attempting to list credentials or set the fido2 PIN using onlykey-cli on NixOS. The onlykey is already initialised, it all works just fine on Ubuntu. |
@Kleptoid You can only list credentials if there are FIDO2 resident credentials to list and a FIDO2 PIN has been set. |
Yes, there are credentials and a pin has been set on the Ubuntu machine, on that machine listing credentials works as expected. On the NixOS machine it doesn't, giving the stated error. It may be a problem with the NixOS package or environment, but since it seems to be happening on someone's Debian as well I though I'd mention it :) |
These prompts are vague and unclear. What exactly am I supposed to do?
I do not know if it is relevant to the main problem, but I also cannot list credentials without getting an error saying
AttributeError: 'Fido2Client' object has no attribute 'client_pin'
I am running the latest version of Debian.
The text was updated successfully, but these errors were encountered: