Skip to content
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

Merged
merged 11 commits into from
Mar 17, 2022
Merged

Less RAM #11

merged 11 commits into from
Mar 17, 2022

Conversation

nickray
Copy link
Member

@nickray nickray commented Mar 5, 2022

The cargo fmt is done at the very end, so the significant changes can be tracked commit by commit.

szszszsz and others added 4 commits February 1, 2022 13:45
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
@nickray nickray changed the title Less ram Less RAM Mar 5, 2022
@nickray nickray mentioned this pull request Mar 5, 2022
@nickray nickray marked this pull request as draft March 5, 2022 21:15
@nickray nickray marked this pull request as ready for review March 17, 2022 02:09
@nickray nickray merged commit d396364 into main Mar 17, 2022
@lobodpav
Copy link

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!

@nickray
Copy link
Member Author

nickray commented Mar 23, 2022

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).

@thegcat
Copy link

thegcat commented Jun 24, 2022

Any news on a release of a new firmware that would render the Solo2 usable on the other half of the internet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants