mirror of
https://git.proxmox.com/git/fwupd
synced 2025-05-14 09:08:16 +00:00
![]() Doing this unconditionally means we accidentally 'bleed' one device mode into another in a non-obvious way. For instance, a device might have two operating modes with different GUIDs. If firmware is supplied for both modes in the same cabinet archive then we might accidentally match the 'wrong' firmware when the daemon has observed a mode switch and added the counterpart GUIDs. We only really need the counterpart GUIDs when switching between Jabra, 8bitdo and DFU devices where the DFU bootloader VID:PID is not manually tagged with `CounterpartGuid` in a quirk file. In the general case lets keep it simple to avoid difficult to find bugs. |
||
---|---|---|
.. | ||
fu-nitrokey-common.c | ||
fu-nitrokey-common.h | ||
fu-nitrokey-device.c | ||
fu-nitrokey-device.h | ||
fu-plugin-nitrokey.c | ||
fu-self-test.c | ||
lsusb.txt | ||
meson.build | ||
nitrokey.quirk | ||
README.md |
Nitrokey Support
Introduction
This plugin is used to get the correct version number on Nitrokey storage devices. These devices have updatable firmware but so far no updates are available from the vendor.
The device is switched to a DFU bootloader only when the secret firmware pin is entered into the nitrokey-app tool. This cannot be automated.
GUID Generation
These devices use the standard USB DeviceInstanceId values, e.g.
USB\VID_20A0&PID_4109&REV_0001
USB\VID_20A0&PID_4109
USB\VID_20A0
Vendor ID Security
The vendor ID is set from the USB vendor, in this instance set to USB:0x20A0
in runtime mode and USB:0x03EB
in bootloader mode.