|0.2.2||Jan 17, 2023|
|0.2.1||Sep 11, 2022|
|0.2.0||May 24, 2022|
|0.1.1||Jan 13, 2022|
|0.0.4||Jul 28, 2021|
#136 in Hardware support
205 downloads per month
This repository is incomplete and under active development.
🐝 solo2 library and CLI
The Solo 2 device can operate in one of two modes (USB VID:PID in brackets):
In regular mode, the PCSC or CTAP interface is used opportunistically.
In maintenance mode, NXP's custom HID protocol is used (via
On Linux, maintenance mode needs udev rules.
You can switch to LPC 55 mode using
solo2 app admin maintenance
You can switch to Solo 2 mode using
solo2 bootloader reboot (or by replugging the device).
Solo 2 is supported by Ludovic Rousseau's CCID driver since release 1.4.35 (July 25, 2021).
Unfortunately, Debian and macOS have not updated yet.
The included Info.plist works.
⚠ DANGER ⚠
If the firmware is invalid according to the bootloader, the device always stays in bootloader mode. This is OK.
BUT: If the firmware is valid according to the bootloader, and the device boots into it, but the firmware has issues (e.g., panics), the only way to get back into bootloader mode and flash a new firmware is by attaching a debugger.
cargo install solo2
For experimental "PKI lite" support, use
cargo install --features dev-pki solo2.
This is not intended to and will not grow into full PKI creation + management functionality,
the goal is only to enable developing and testing all functionality of all official apps.
If the key is in regular mode, and its firmware contains the admin app:
solo2 app admin uuidreads out the serial number.
solo2 app admin maintenanceswitches to bootloader mode.
If the key is in regular mode, and its firmware contains the NDEF app:
solo2 app ndef capabilitiesreads out the NDEF capabilities.
If the key is in maintenance mode:
solo2 bootloader rebootswitches to regular mode (if the firmware is valid).
Note that subcommands are inferred, so e.g.
solo2 b r works like
solo2 bootloader reboot.
pretty_env_logger, configured via
-v logs INFO and
DEBUG level logs.
SoloKeys is fully open source.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
All hardware, unless otherwise noted, is licensed under CERN-OHL-S-2.0.
All documentation, unless otherwise noted, is licensed under CC-BY-SA-4.0.