argyle-software / dilithium Goto Github PK

Ensure the library is tested on a big endian system during CI

Add a benchmarking suite, preferably with criterion

It looks like there's no way to save/restore a Keypair. I guess this is nowhere even near production ready right?

I set out to use this library in a certificate validation library but ran into issues trying to support any of modes 2, 3 and 5. I refactored a fork of the library to use proc macros to allow generating independent implementations and changed the features so all three can be used simultaneously. A copy is here: https://github.com/carl-wallace/dilithium/tree/macros. I have confirmed I can verify certificate signatures for each mode in a WASM project, but have not done any testing beyond that as yet. Any thoughts on the desire to use > 1 mode (did I miss something that made that possible as it was?) or on using proc macros to achieve this end?

Add a wasm api and package for publishing to npm

Library should have a BYO RNG setup, with RngCore + CryptoRng trait bounds.

I'm trying to use the library with an ARM Cortex M4 and I'm having problems with the dilithium library's getrandom crate because the error message says:
the thumbv7em-none-eabi target may not support the standard library

Since the embedded systems compatibility is not specified in the Readme, I wanted to kindly ask if the library is designed to work in a no_std environment?

Thanks