mirror of
https://git.proxmox.com/git/fwupd
synced 2025-05-28 11:23:04 +00:00
![]() Before this change calling FuUsbDevice->open() opened the device, and also unconditionally added various GUIDs and InstanceIDs which we normally do in setup. Then fu_device_setup() would call the FuSubclass->setup() vfunc which would have no way of either opting out of the FuUsbDevice->setup()-like behaviour, or controlling if the parent class ->setup is run before or after the subclass setup. Split up FuUsbDevice->open() into clear ->open() and ->setup() phases and add the parent class calls where appropriate. This means that ->setup() now behaves the same as all the other vfuncs. |
||
---|---|---|
.. | ||
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
.