v0.4.12.nitrokey

Support Nitrokey 3 firmware update - automatic download (fix)

v0.4.11.nitrokey-2-g9f3b9f1

Bump version to 0.4.12

v0.4.10.nitrokey

This release supports Nitrokey 3 firmware update.

v0.4.9.nitrokey

Avoid scanning for devices when device handle is provided

v0.4.8.nitrokey

Support for Nitrokey 3

v0.4.5.nitrokey

Extend logging for Nitrokey Start firmware update

v0.4.4.nitrokey

Initial support for the Nitrokey Pro firmware update

v0.4.3.1

Merge branch 'fix-versioning'

Bugfix (Pre)-Release

• add experimental hint for make-credential and disable challenge-response
• fido2 util program is also a work-in-progress
• pin handling fixes (likely to break soon as fido2 master branch already has PinClientV2 and a generic one)
• updated minimal required version for fido2
• various installation/dependency checks improvements (#43)
• fido2 reset now informs the user about how the reset process should be executed
• fido2 reboot informs the user about the needed device-key confirmation
• add all connected (Nitrokey) devices into log on error (local_critical() with support_hint==True) (#35)
• experimental windows .msi installer release (use with care!)

Restructuring and Feature (Pre)-Release

Keep in mind that this software is still in alpha-stage with this release.
Most regular functions are working, but especially the lower-level functions
show issues with the 2.1 NK-Fido2 firmware.

For now the release is exclusively available via pip.
A Windows installer/standalone and potentially other will be part of one of the following releases and the following ones.

Known issues:

• fido2 reboot not working

  • fido2.ctap.CtapError: CTAP error: 0x01 - INVALID_COMMAND

• fido2 reset not working

  • fido2.ctap.CtapError: CTAP error: 0x30 - NOT_ALLOWED is returned, if the command is executed after first 10 seconds of device's power cycle - it has to be reinserted to the USB slot;

• fido2 util program bootloader nitrokey-fido2-firmware-2.0.0.json

  • fails due to not being able to reboot, but works the 2nd time, as the device is already in bootloader mode

• fido2 util program aux leave-bootloader

  • same as: program aux reboot (potentially)

• start set-identity X

  • spurious connection issues
  • might also need a sudo systemctl stop pcscd pcscd.socket, (as in start update) but this is not really a long term feasible solution