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

virt: adapt to trussed-dev/littlefs2#24 #12

Open
wants to merge 50 commits into
base: main
Choose a base branch
from
Open

Conversation

daringer
Copy link

@daringer daringer commented Feb 6, 2023

see: trussed-dev/littlefs2#24

enables usbip to work with the above changes/PR

sosthene-nitrokey and others added 30 commits November 23, 2022 11:10
The `rng` feature is replaced by rand_chacha
In a separate commit for better visibility.

Removed addressed TODOs, reworded those that should stay for later (magic numbers),
rebased to the latest "main".

Signed-off-by: alt3r 3go <[email protected]>
rsa2k -> rsa2048
rsa3k -> rsa3072
rsa4k -> rsa4096
sosthene-nitrokey and others added 20 commits November 23, 2022 11:10
Fido-authenticator depended on its length. This commit restores the old length changes only the length of the (de)serialize_key methods to minimize breakage
As RSA requires an allocator, it  should no be enabled by default
This reverts commit 2909643.

The update breaks the format and causes loss of existing U2F keys
In #38 [0], we restricted the operations for the hmacsha256 mechanism
to symmetric and shared keys.  This breaks fido-authenticator because it
uses hmacsha256 derive_key on EC keys [1].  This patch relaxes the
restrictions to allow all key kinds.

[0] trussed-dev#38
[1] trussed-dev/fido-authenticator#21
For our fork, we don’t need to check compatibility with solokeys.  And
the nitrokey-3-firmware check isn’t active anyway.
This is required for compatibility with nitrokey-3-firmware.
Patch littlefs2 dependency
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