| Mattias Nissler | fca75c8 | 2016-03-22 15:27:15 +0100 | [diff] [blame] | 1 | libconstrainedcrypto provides a random set of basic crypto algorithms |
| 2 | originating from Google-internal code. |
| 3 | |
| 4 | This is *NOT* a general purpose crypto library. Our goal is to standardize on |
| 5 | only one native crypto library for the Android platform, and that library is |
| 6 | BoringSSL. Wherever possible, you should prefer BoringSSL's libcrypto over |
| 7 | libconstrainedcrypto. In particular, all code running in Android user space |
| 8 | should use BoringSSL. |
| 9 | |
| 10 | There a few rare exceptions where BoringSSL is can't be used yet (such as |
| 11 | bare-bones bootloaders etc.). There is a plan to reduce BoringSSL' libcrypto's |
| 12 | dependency footprint to make libcrypto usable in these environments as well |
| 13 | though. |
| 14 | |
| 15 | A number of projects still rely on libconstrainedcrypto (formerly known as |
| 16 | libmincrypt) due to historic reasons, the goal is to clean these up and switch |
| 17 | them over to BoringSSL wherever possible. |