hi team, thank you for all your work on libcrux.
If I understand correctly, 8dfe4ec introduced a required sys_rng / getrandom dependency to hpke-libcrux-rs. We build a crate that uses the libcrux provider and targets multiple architectures including wasm32-unknown-unknown, and ideally we'd avoid rand and getrandom in that crate and let the consumer crates that we are building supply their own architecture-specific randomness choice rather than require it in our shared crate.
Is this something you'd be open to supporting again in libcrux_provider? Thank you and let me know if you need any more information!
hi team, thank you for all your work on libcrux.
If I understand correctly, 8dfe4ec introduced a required
sys_rng/ getrandom dependency to hpke-libcrux-rs. We build a crate that uses the libcrux provider and targets multiple architectures includingwasm32-unknown-unknown, and ideally we'd avoidrandandgetrandomin that crate and let the consumer crates that we are building supply their own architecture-specific randomness choice rather than require it in our shared crate.Is this something you'd be open to supporting again in libcrux_provider? Thank you and let me know if you need any more information!