FIDO2 SSH key + certificate authentication
Extends v5.28.0's step-ca cert path to FIDO2 sk-keys. A hardware-resident
ed25519-sk or ecdsa-sk key signed by a CA can now authenticate against
servers with TrustedUserCAKeys configured — the certificate is advertised
as sk-*-cert-v01@openssh.com while signing still goes through the
authenticator (USB / NFC / built-in security key).
The path that was previously cert-aware only for software keys (via JSch's
OpenSshCertificateAwareIdentityFile, which assumes a software identity
file) now wraps the live FidoIdentity in a CertificateWrappedIdentity
so the cert blob and the hardware signature can travel together.
Attach-time certificate validation
"Attach certificate" in Keys now uses a real cert parser instead of the
prefix-only header check. Mistakes that previously surfaced as opaque
auth failures at connect time now fail loudly in the import dialog:
- The cert's embedded public-key fingerprint must match the target key —
catches "wrong cert for this key" mistakes in the Keys tab rather than
on the wire. - Validity window is checked: an expired cert still attaches but with a
visible warning, so you can pre-stage a renewal. - On success, the cert's
valid_principalslist is surfaced in the
attach toast — confirms which login names the cert authorizes you for.
Works for software RSA / ECDSA / Ed25519 keys and for FIDO2 ed25519-sk /
ecdsa-sk keys.
MCP
open_file_in_editortool — opens a file in the host editor over MCP.- SFTP browser tool gains a folder filter for tighter prompts.
Credits
The FIDO2 + cert plumbing and the cert parser are the work of @pinpox
(PR #136) — picked up here
on top of v5.28.0's step-ca foundation. Closes #134.
Install
- Direct: APKs attached below (arm64 + x64).
- F-Droid: the bot will pick this tag up automatically; the F-Droid
client should offer the update once linsui merges the bot's MR.
Full Changelog: v5.28.0...v5.29.0