(Nitrokey 3 - Windows)
This guide describes how to update the firmware on the Nitrokey 3.
For firmware v.1.0.0 and below the update will delete all user data! Make sure you have proper backup login methods enabled and/or ensure that the Nitrokey 3 is not the only way to authenticate/2FA for your applications/services.
For firmware v1.0.1 and above user data is retained during the update. Anyways, be sure to always have another device (or login method) registered with your service, if for some reason your data is not retained.
Never disconnect the Nitrokey 3 or abort the process while updating, this will likely render your device useless!
Make sure you have the latest pynitrokey version installed, please check the installation instructions for your OS.
nitropy nk3 update.
Once instructed by
nitropytouch the device to activate bootloader.
macOS only: If instructed by
nitropyrun update command again.
Please wait until the process finished. (This may vary depending on your operating system)
nitropy nk3 testto check if device is working properly after flashing.
In case of any errors please take the logs from
/tmp directory (
There are three types of firmware releases for the Nitrokey 3:
Stable releases are most important for users. They are designed to be backward compatible and to retain all user data and are thoroughly tested. On production devices, only stable releases should be used.
A release candidate is a preview of an upcoming stable release. It should also be backward compatible but is not tested as thoroughly as a stable release.
Test releases (previously: alpha releases) contain additional features that are not ready for production yet. User data created with a test release may not be compatible with other releases. These releases are still being tested and are more likely to contain bugs.
See the release notes on GitHub for more information on the features available in a release.
You can identify the type of a firmware release by its version number:
The firmware of the Nitrokey 3 cannot be downgraded. You can only install a firmware update with the same or a higher major, minor and patch version number than the firmware currently installed on the device. This protects against downgrade attacks where a secure firmware version would be replaced with an old, potentially insecure version.
v1.3.1can be updated to
v1.3.1-test.20230414and vice versa because they have the same major, minor and patch version number.
v1.3.1can be updated to
v1.4.0because the version number increases.
v1.3.1cannot be updated to
v1.3.0-rc.1because the version number would decrease.
This is mostly relevant for users that rely on a feature from the test releases. Users of the stable firmware can always update to the latest available firmware version.