Passkey portability and FIDO 2.3 in Pico FIDO 8
Pico FIDO 8 lets users move selected resident passkeys between enrolled devices through Pico Vault. It also updates encrypted storage and adds FIDO 2.3 features, with tests across FIDO, OATH, OTP, and Vault.
Export and import credentials with Pico Vault
Pico Vault exports a selected resident credential as an authenticated, opaque PKV1 package for import on another enrolled Pico FIDO device. Ordinary desktop software does not receive the private key in plaintext. Keep the package for backup or replacement-device recovery without copying the whole authenticator.
- Enrollment is protected by PIN authorization and a physical-button ceremony.
- Vault enrollment supports certificate-backed device identity and board binding.
- Credential metadata is exported alongside the credential because it cannot be reconstructed from the private key alone.
- Imported credentials are kept distinct from native credentials and do not transplant or advance the destination device’s native signature counter.
- Four authenticated encryption profiles are available: ChaCha20-Poly1305, AES-GCM, and both two-layer combinations.
- Legacy Vault commands have been removed in favor of the consolidated flow.
Pico Vault is an opt-in vendor feature. Standard WebAuthn and CTAP sign-ins keep working as before. Keep the Vault key, exported packages, PIN, and enrollment material with your recovery records.
FIDO and WebAuthn improvements
- FIDO 2.3 is now announced and exercised by the test suite.
- Added or expanded coverage for `thirdPartyPayment`, `uvm`, `minPinLength`, `maxPINLength`, and related authenticator configuration behavior.
- Added configurable PIN complexity rules that can require uppercase letters, lowercase letters, digits, symbols, or combinations of these patterns.
- Added configurable `alwaysUv`, `makeCredUvNotRqd`, and non-resident-credential policies, with matching `getInfo` reporting.
- Added a configurable policy to deny creation of resident/discoverable credentials when only non-resident credentials are permitted.
- Added per-credential expiration and revocation controls: credentials can be automatically rejected after expiry or explicitly revoked.
- Improved credential management, including RP/token binding and support for large credential sets.
- Improved large-blob validation, integrity checking, authentication, and transfer-state cleanup.
- Improved HID channel handling, cancellation, selection, and next-assertion behavior.
Security and reliability
This release adds storage and authorization checks for resident credentials, OATH, and OTP.
- Resident credentials, OATH credentials, and OTP slots use authenticated object containers with compatibility handling for existing layouts.
- RP identifiers and OATH/OTP secrets receive stronger at-rest protection.
- Imported credentials use a dedicated resident-container path with atomic persistence and recovery-oriented fault handling.
- Added operation-scoped object authorization evidence and tighter filesystem publication ordering.
- Hardened length, bounds, transport-array, CBOR, protocol, and credential-ID validation across FIDO, OATH, OTP, backup, configuration, and Vault paths.
- PIN retry state survives power loss more reliably; failed PIN operations regenerate authorization tokens and stale authorization state expires correctly.
- Configuration writes, backup restore, password-safe reads, and sensitive OATH operations require the appropriate authentication and physical presence.
- Corrected reset, U2F/`alwaysUv`, credential-counter, and error-reporting edge cases.
OATH and OTP
OATH and OTP changes:
- Encrypted storage now covers complete OTP slots and protected OATH access.
- HOTP operations enforce touch and authorization requirements consistently.
- HOTP verification, decrement behavior, slot swaps, access-code checks, and password-safe reads are more strictly validated.
- OATH and OTP data now use the same authenticated container direction as the FIDO credential store.
Conformance and testing
Tests now cover FIDO 2.3, credential management, silent authentication, metadata, HID, OATH, OTP, object containers, storage compatibility, and Pico Vault.
An internal run of the FIDO Alliance Conformance Test App reported 251 passes and 0 failures. The test environment skipped some checks, so this is not certification. FIDO Alliance certification requires a separate process.
Pico Vault tests cover all four encryption profiles, malformed and tampered packages, wrong-vault rejection, enrollment protection, credential metadata, and live export/import round trips when an enrolled device is available.
SDK, storage, and transport changes
- Refreshed the bundled PicoKeys SDK with versioned filesystem envelopes, bounded authenticated object records, atomic transactions, namespace-aware handles, policy checks, separate integrity roots, and legacy-layout access for migration.
- Expanded the shared filesystem for multi-sector files, 32-bit lengths, dynamic indexing, and cache draining, supporting larger and more resilient encrypted stores.
- Hardened shared APDU, USB, CCID, and secure-messaging paths with stricter length checks, safe response chaining, bounded buffers, timeout handling, and safer flash publication and commit behavior.
- Resident, OATH, and OTP data moved onto the PicoKeys SDK object-container infrastructure, including authenticated manifests, migration compatibility, and crash-safe updates.
- Credential key derivation now uses stable resident identifiers, preserving related key material across supported operations.
- PKV1 uses a vault-derived identity, authenticated headers, per-credential key separation, and X448/HKDF-based enrollment support.
- The emulator and build system gained better MSVC and RP2040/RP2354 support, refreshed SDK and library integration, and additional Windows test launchers.
- CI and CodeQL workflows were hardened, and metadata was updated for the v8.0 authenticator profile.
Upgrade note
Pico FIDO 8 changes credential storage and adds migration-aware container handling. Before upgrading a device with important credentials, confirm that you have a tested recovery path. Pico Vault recovery is available only for credentials exported while the source device is available, with the corresponding Vault material preserved.
