mirror of
https://git.proxmox.com/git/fwupd
synced 2025-08-06 09:00:55 +00:00
![]() This allows us to 'nest' firmware formats, and removes a ton of duplication. The aim here is to deprecate FuFirmwareImage -- it's almost always acting as a 'child' FuFirmware instance, and even copies most of the vfuncs to allow custom types. If I'm struggling to work out what should be a FuFirmware and what should be a FuFirmwareImage then a plugin author has no hope. For simple payloads we were adding bytes into an image and then the image into a firmware. This gets really messy when most plugins are treating the FuFirmware *as* the binary firmware file. The GBytes saved in the FuFirmware would be considered the payload with the aim of not using FuFirmwareImage in the single-image case. |
||
---|---|---|
.. | ||
data | ||
fu-plugin-solokey.c | ||
fu-solokey-device.c | ||
fu-solokey-device.h | ||
fu-solokey-firmware.c | ||
fu-solokey-firmware.h | ||
meson.build | ||
README.md | ||
solokey.quirk |
SoloKey Support
Introduction
The SoloKey Secure and Hacker is an affordable open source FIDO2 security key.
All hardware supports the U2F HID flashing protocol. The Hacker version is not supported and the existing DFU update procedure should be used.
Firmware Format
The daemon will decompress the cabinet archive and extract a firmware blob in a JSON wrapped, base-64, Intel hex file.
This plugin supports the following protocol ID:
- com.solokeys
GUID Generation
These devices use the standard USB DeviceInstanceId values, e.g.
USB\VID_0483&PID_A2CA&REV_0001
USB\VID_0483&PID_A2CA
Update Behavior
The firmware is deployed when the device is in normal runtime mode, and the device will reset when the new firmware has been written.
Vendor ID Security
The vendor ID is set from the USB vendor, in this instance set to USB:0x0483
External interface access
This plugin requires read/write access to /dev/bus/usb
.