fwupd/plugins/solokey/README.md
Richard Hughes 078beafb2d Add a new internal flag to opt-in to GUID matching
It is far too easy to forget to set FWUPD_DEVICE_FLAG_NO_GUID_MATCHING for new
plugins, and without it it all works really well *until* a user has two devices
of the same type installed at the same time and then one 'disappears' for hard
to explain reasons. Typically we only need it for replug anyway!

Explicitly opt-in to this rarely-required behaviour, with the default to just
use the physical and logical IDs. Also document the update behavior for each
plugin to explain why the flag is being used.

This allows you to have two identical Unifying plugged in without one of them
being hidden from the user, at the same time allowing a HIDRAW<->USB transition
when going to and from bootloader and runtime modes.

This removes the workaround added in 99eb3f06b6.

Fixes https://github.com/fwupd/fwupd/issues/2915
2021-02-25 15:47:25 +00:00

1.0 KiB

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.