You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the latest version of x25519-dalek-ng (v1.1.1) does not compile to a no-std target like thumbv7em-none-eabihf because it doesn't disable the default features of its rand dependency and that brings in a dependency on libstd due to its opt-out "std" feature. I can certainly send a fix for that but given that the repository / crate has not been updated / released since early 2021, it's possible that the fix never makes it into a release.
would it be possible to use x25519-dalek instead of the -ng one? the former has proper no-std support and seems to be more actively maintained.
The text was updated successfully, but these errors were encountered:
On that crypto provider in general: This crypto provider is really here for convenience but I don't use it too much myself. I know these crates are popular, but I generally recommend using other crypto libraries that don't lead to a dependency hell like this. The everest provider is not maintained anymore and I'll remove it. But I'll add a libcrux one soon.
the latest version of x25519-dalek-ng (v1.1.1) does not compile to a no-std target like
thumbv7em-none-eabihf
because it doesn't disable the default features of itsrand
dependency and that brings in a dependency on libstd due to its opt-out "std" feature. I can certainly send a fix for that but given that the repository / crate has not been updated / released since early 2021, it's possible that the fix never makes it into a release.would it be possible to use
x25519-dalek
instead of the -ng one? the former has proper no-std support and seems to be more actively maintained.The text was updated successfully, but these errors were encountered: