-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Less RAM #11
Conversation
Some services do not accept arbitrary long key handle (aka Credential ID), which makes the FIDO operations failing. This patch removes some fields from credential data serialization while making credential ID, and with this it reduces key handle size by around 30% (from ~320 to ~220 using test site [1]). Tested on Gitlab, and this patch makes it working correctly (both registering and signing, as opposed to 500 error code returned otherwise). Presumably the hidden limit is 255 bytes, which would be compatible with CTAP1. Resident Keys stay the same, with full metadata stored on the device. [1] webauthn.bin.coffee
Probably a dumb question, but anyway - may I ask how do I get notified when this change gets its way to the firmware release? Having issues with too long key handle in a few services. Thanks! |
You can "Watch for releases" of https://github.com/solokeys/solo2 (top-right, watch, custom, releases) or check the https://github.com/solokeys/solo2/releases page by hand, for now. I have a firmware that's basically ready except I don't have a working NFC testing setup and I think I may have borked it (as this firmware "doesn't work" on my Pixel 5). |
Any news on a release of a new firmware that would render the Solo2 usable on the other half of the internet? |
The
cargo fmt
is done at the very end, so the significant changes can be tracked commit by commit.