- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Alternatives may be found - not in any specific order:
- [libsodium-sys-stable](https://crates.io/crates/libsodium-sys-stable) - [dryoc](https://crates.io/crates/dryoc) - [RustCrypto/nacl-compat](https://github.com/RustCrypto/nacl-compat) (`crypto_box`, `crypto_kx`, `crypto_secretstream`) - [RustCrypto/xsalsa20poly1305](https://github.com/RustCrypto/AEADs/tree/master/xsalsa20poly1305) (`crypto_secretbox`) - [Signatory](https://crates.io/crates/signatory) - [ed25519-compact](https://crates.io/crates/ed25519-compact) - [ed25519-dalek](https://github.com/dalek-cryptography/ed25519-dalek) - [ring](https://github.com/briansmith/ring)
Recommendations can be also found from:
- [Awesome Rust Cryptography](https://github.com/The-DevX-Initiative/RCIG_Coordination_Repo/blob/main/Awesome_Rust_Cryptography.md)
No direct maintained fork exists.
Patch / fix
Is RUSTSEC-2021-0137 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | sodiumoxide | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.