Trussed® firmware
➡ Discussion: #129
WARNING! This update will invalidate any existing credentials you have on your authenticator. This is to solve a credential encoding length we had before.
- Credential ID lengths exceeded 255 bytes which caused issues for some platforms and whenever U2F is used. Lengths are now shorter than 255.
- Fixed problematic use of wait uptime messages
- Fixed U2F issue with NFC treating APDUs incorrectly
- Fixed LED to work as intended (green pulse for OK, blue/purple to ask for user touch, red for "dead")
This release 2:20220822.0 switches versioning schemes to "date-versioning" (era:date.patch). The prefix 2: means that this is a breaking change vs. previous 1: releases, and the date 20220822 denotes when it was built (in this case August 22, 2002 - later is better). The suffix .0 would only be needed in case of multiple releases on one day. Hence with the CLI tool, running solo2 ls easily shows how current the firmwares are. For technical reasons, in some places an associated semantic versioning (in this case, X.Y.Z = 2.964.0) may be visible. These convert via era = X, date = 2020-01-01 + Y, patch = Z. That is, Y means days since the start of 2020.
Breaking change means that your FIDO credentials will likely stop working (existing TOTP credentials, if any, are not affected). So, ensure you have alternate ways to login to your sites, and re-register the device after updating it. You can "wipe" a device using fido2-token -R (in the future, the CLI will also implement this).