allwinner_a64/android/external/libconstrainedcrypto
2018-08-08 16:14:42 +08:00
..
include/constrainedcrypto upload android base code part2 2018-08-08 16:14:42 +08:00
test upload android base code part2 2018-08-08 16:14:42 +08:00
Android.bp upload android base code part2 2018-08-08 16:14:42 +08:00
dsa_sig.c upload android base code part2 2018-08-08 16:14:42 +08:00
MODULE_LICENSE_BSD upload android base code part2 2018-08-08 16:14:42 +08:00
NOTICE upload android base code part2 2018-08-08 16:14:42 +08:00
p256.c upload android base code part2 2018-08-08 16:14:42 +08:00
p256_ec.c upload android base code part2 2018-08-08 16:14:42 +08:00
p256_ecdsa.c upload android base code part2 2018-08-08 16:14:42 +08:00
README upload android base code part2 2018-08-08 16:14:42 +08:00
README.version upload android base code part2 2018-08-08 16:14:42 +08:00
rsa.c upload android base code part2 2018-08-08 16:14:42 +08:00
sha.c upload android base code part2 2018-08-08 16:14:42 +08:00
sha256.c upload android base code part2 2018-08-08 16:14:42 +08:00

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.