gecko-dev/third_party/rust/rc_crypto
Mark Hammond 6abadd577b Bug 1639449 - Vendor new application-services to expose kinto migration and sync change notifications. r=lina
Differential Revision: https://phabricator.services.mozilla.com/D76092
2020-05-30 02:44:07 +00:00
..
src Bug 1631630 p1 - Vendor fxa-client crate. r=rfkelly,mhoye 2020-05-16 01:07:28 +00:00
.cargo-checksum.json Bug 1639449 - Vendor new application-services to expose kinto migration and sync change notifications. r=lina 2020-05-30 02:44:07 +00:00
Cargo.toml Bug 1639449 - Vendor new application-services to expose kinto migration and sync change notifications. r=lina 2020-05-30 02:44:07 +00:00
README.md Bug 1631630 p1 - Vendor fxa-client crate. r=rfkelly,mhoye 2020-05-16 01:07:28 +00:00

README.md

rc_crypto

The rc_crypto crate, like its name implies, handles all of our cryptographic needs.

For consumers, it pretty much follows the very rust-idiomatic ring crate API and offers the following functionality:

Under the hood, it is backed by Mozilla's NSS library, through bindings in the nss crate. This has a number of advantages for our use-case:

Rust features

  • gecko will avoid linking against libsqlite3_sys's libsqlite. See #2882 for context.