You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sandy
99da0f2c72
|
4 years ago | |
|---|---|---|
| .. | ||
| include/constrainedcrypto | 4 years ago | |
| test | 4 years ago | |
| Android.bp | 4 years ago | |
| MODULE_LICENSE_BSD | 4 years ago | |
| NOTICE | 4 years ago | |
| README | 4 years ago | |
| README.version | 4 years ago | |
| dsa_sig.c | 4 years ago | |
| p256.c | 4 years ago | |
| p256_ec.c | 4 years ago | |
| p256_ecdsa.c | 4 years ago | |
| rsa.c | 4 years ago | |
| sha.c | 4 years ago | |
| sha256.c | 4 years ago | |
README
libconstrainedcrypto provides a random set of basic crypto algorithms
originating from Google-internal code.
This is *NOT* a general purpose crypto library. Our goal is to standardize on
only one native crypto library for the Android platform, and that library is
BoringSSL. Wherever possible, you should prefer BoringSSL's libcrypto over
libconstrainedcrypto. In particular, all code running in Android user space
should use BoringSSL.
There a few rare exceptions where BoringSSL is can't be used yet (such as
bare-bones bootloaders etc.). There is a plan to reduce BoringSSL' libcrypto's
dependency footprint to make libcrypto usable in these environments as well
though.
A number of projects still rely on libconstrainedcrypto (formerly known as
libmincrypt) due to historic reasons, the goal is to clean these up and switch
them over to BoringSSL wherever possible.