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

rand_core v0.9 support #1642

Open
4 tasks
tarcieri opened this issue Aug 8, 2024 · 5 comments
Open
4 tasks

rand_core v0.9 support #1642

tarcieri opened this issue Aug 8, 2024 · 5 comments

Comments

@tarcieri
Copy link
Member

tarcieri commented Aug 8, 2024

UPD: The migration is mostly complete. Remaining crates:

@tarcieri
Copy link
Member Author

tarcieri commented Aug 8, 2024

Edit: see original version of toplevel description for context

I think option 2 is probably the most straightforward. It's pretty much where we were before, and we have also added getrandom-based fallible APIs.

@newpavlov
Copy link
Member

newpavlov commented Aug 8, 2024

I think we can have two sets of methods: one set based on CryptoRng and another set of try_* methods based on TryCryptoRng. Note that fallible RNGs should implement the Try* traits, while potentially fallible ones can be converted to "infallible" using the UnwrapErr wrapper. Users then can decide what to use by themselves.

@tarcieri
Copy link
Member Author

rand_core v0.9 is out

@baloo
Copy link
Member

baloo commented Feb 14, 2025

kem will need to be excluded from the workspace for a little while. It depends on x3dh-ke which depends on ecdsa. There is a bit of a release dance that will need to happen.

@tarcieri
Copy link
Member Author

@rozbb perhaps we can get rid of the dev-dependencies of the kem crate now that its API has been massively simplified?

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

No branches or pull requests

3 participants