Repository navigation
Soft-Lock questions #113
|
https://github.com/TheMaxMur/RS-Key/blob/main/docs/guides/soft-lock.md Is it a standard fido feature? Does any other key implement a similar function? |
Replies: 2 comments 1 reply
|
No, Soft-Lock is not a standard FIDO/CTAP feature. It is an RS-Key-specific extension. FIDO defines I am not aware of another mainstream FIDO security key implementing exactly the same model: a separate randomly generated 256-bit key, kept by the user, which must be supplied after every power cycle before the FIDO master seed becomes usable. Other keys obviously protect credentials at rest and may use PINs or hardware secure storage, but that is a different mechanism. Soft-Lock does not burn RP2350 OTP fuses. The OTP fuses are only involved in the separate production-hardening procedure used for the device root key / secure boot. Soft-Lock itself only changes records in normal flash storage. So there is no OTP-fuse counter or one-time limit associated with it. You can rotate the Soft-Lock key by unlocking, disabling the lock, and enabling it again; The only practical lifetime consideration is ordinary flash wear, since enabling/disabling writes to flash. Rotating it once a week is nowhere near the kind of write frequency I would worry about. One caveat: because RS-Key uses log-structured flash storage, an obsolete plaintext-sealed seed record may physically remain in old flash pages until compaction overwrites it. It is still encrypted/sealed with the device root, but this is why the documentation says the at-rest guarantee after enabling Soft-Lock hardens over time rather than becoming physically instantaneous. |
|
Ok, im looking at the client implementation in https://github.com/TheMaxMur/RS-Key/blob/main/tools/rsk/lock.py Its cool that you use random keys, stronger than passphrases or pins in theory. This still exposes your softlock key to the machine using the key. Just like the pin. That would be my main reason to rotate the softlock key periodically. Would a public key implementation be viable? Something like
It would still give the option to unlock with the soft-lock key, but would not expose it to rsk directly. X25519 is part of the webcrypto api, a third party tool would be very straightforward, i can do it myself... |
No, Soft-Lock is not a standard FIDO/CTAP feature. It is an RS-Key-specific extension.
FIDO defines
authenticatorConfig, but the standardized subcommands are things such astoggleAlwaysUv,setMinPINLength, enterprise attestation, etc. There is also a vendor-specific configuration space, which is where features like this conceptually belong. Soft-Lock uses the existing FIDO PIN /acfgauthorization machinery for enabling and disabling it, but the actual seed-wrapping and unlock mechanism is specific to RS-Key.I am not aware of another mainstream FIDO security key implementing exactly the same model: a separate randomly generated 256-bit key, kept by the user, which must be supplied after …