-
Notifications
You must be signed in to change notification settings - Fork 29
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
nk3 update: Wrong nonce error if Nitrokey App 2 is running #624
Comments
Thanks for the report! Can you please share the log file mentioned in the error message? |
(transfering this issue to pynitrokey, as this is not app2) generally this looks like the update went through without issues, the finalization step is only "waiting for the device to re-appear" - nevertheless this shouldn't happen |
https://gist.github.com/hkienle/88c6fc86ea0354447a53f6b7295d98cf |
Thank you! I don’t think I’ve seen this kind of error before. Did this happen only once or have you seen it multiple times? Are there any other processes that could have tried to access the device? Was the Nitrokey App 2 running at the same time? The relevant snippets from the log
|
I tried this only once. Yes, I think the Nitrokey App 2 was running when I tried this. I can try again if you want, let me know. |
I think it’s likely caused by Nitrokey App 2 and nitropy both listening for new devices (Nitrokey App 2 does this all the time, nitropy does it after the firmware update). So when the device reboots after the update, both try to initialize communication with the device, leading to this error. I’ll try to reproduce it on my side. |
Indeed this seems to be the cause. I can reproduce the error by:
Next steps:
Error
|
Since updating to the same version is offered by
nitropy
, I assume it is supported and should succeed!?I have a Nitrokey 3A NFC.
The text was updated successfully, but these errors were encountered: