NK3: Update 1.7.2 -> 1.8.0 not working

Nitrokeys FIDO2 / Nitrokey 3
1

Hallo,
I updated without issues in the past (udev etc. is all correct), but now it is not working anymore.
Nitrokey firmware (currently): 1.7.2
Nitrokey firmware (planned update): 1.8.2
pynitrokey==0.7.0

I get the following error. The error happens after touching the key to enter bootloader mode.

nitropy nk3 update
Command line tool to interact with Nitrokey devices 0.7.0
Do you want to download the firmware version v1.8.0? [Y/n]: y
Download v1.8.0: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1.08M/1.08M [00:00<00:00, 5.63MB/s]
Current firmware version: v1.7.2
Updated firmware version: v1.8.0

Please do not remove the Nitrokey 3 or insert any other Nitrokey 3 devices during the update. Doing so may damage the Nitrokey 3.
Do you want to perform the firmware update now? [y/N]: y

Please press the touch button to reboot the device into bootloader mode …

Critical error:
An unhandled exception occurred
Exception encountered: SPSDKConnectionError()

Critical error occurred, exiting now
Unexpected? Is this a bug? Would you like to get support/help?

Unfortunately reexecuting the command does not work. Also booting before in bootloader mode does not work (entering bootloader mode does not trigger the error).

Any ideas?

2

We are currently investigating this problem. See this GitHub issue for more information and updates: nk3: `SPSDKConnectionError` during `nitropy nk3 update` (with udev rules in place!) · Issue #601 · Nitrokey/pynitrokey · GitHub

3

There was a breaking change in a dependency. v0.7.1 should fix the problem.

4

same same, but different, happens with my nitrify v0.7.1:
21:57 [~]$ nitropy nk3 update
Command line tool to interact with Nitrokey devices 0.7.1
Do you want to download the firmware version v1.8.0? [Y/n]: Y
Download v1.8.0: 100%|██████████████████████████████████████████████████████████████████████████| 1.08M/1.08M [00:00<00:00, 8.35MB/s]
Current firmware version: v1.7.2
Updated firmware version: v1.8.0

Please do not remove the Nitrokey 3 or insert any other Nitrokey 3 devices during the update. Doing so may damage the Nitrokey 3.
Do you want to perform the firmware update now? [y/N]: y

Please press the touch button to reboot the device into bootloader mode …

Perform firmware update: 100%|████████████████████████████████████████████████████████████████████| 534k/534k [00:23<00:00, 23.1kB/s]
Finalize upgrade: 10%|███████▊ | 10/100 [00:07<01:08, 1.31%/s]
Critical error:
An unhandled exception occurred
Exception encountered: OSError(‘Failed reading a response’)
Warning: no backend was found to use for communication. Please refer to documentation how to install additional libraries.

Critical error occurred, exiting now
Unexpected? Is this a bug? Would you like to get support/help?

  • You can report issues at: https://support.nitrokey.com/
  • Writing an e-mail to support@nitrokey.com is also possible
  • Please attach the log: ‘/var/folders/bz/b81y31v50y583fw07qpswyfr0000gn/T/nitropy.log.luza4zim’ with any support/help request!
5

for me version 0.7.1 worked and I did not face the issue of rajo

6

What happened afterwards? Can you please send me the log file /var/folders/bz/b81y31v50y583fw07qpswyfr0000gn/T/nitropy.log.luza4zim (post here or mail to support@nitrokey.com)?

7

there is no log nitropy.log.luza4zim, but 3 others, see attachment.

03:59 [~]$ nitropy nk3 test
Command line tool to interact with Nitrokey devices 0.7.1
Found 1 NK3 device(s):

  • Nitrokey 3 at 4294971915

Running tests for Nitrokey 3 at 4294971915

[1/5] uuid UUID query SUCCESS 37D8A01CB2D148A10000000000000000
[2/5] version Firmware version query SUCCESS v1.8.0
[3/5] status Device status SUCCESS Status(init_status=<InitStatus.0: 0>, ifs_blocks=241, efs_blocks=470, variant=<Variant.NRF52: 2>)
Running SE050 test: |
[4/5] se050 SE050 SUCCESS SE050 firmware version: 3.1.1 - 1.11, (persistent: (28512,), transient_deselect: (607,), transient_reset: (592,))
Please press the touch button on the device …
Please press the touch button on the device …
[5/5] fido2 FIDO2 SUCCESS

5 tests, 5 successful, 0 skipped, 0 failed

Summary: 1 device(s) tested, 1 successful, 0 failed

Apparently the termination did not have any serious consequences.
Yours sincerely,

Alfred Herrmann

(attachments)

logs.zip (2.51 KB)