| commit | ad6d33c70dd18bdd90f0dcce3324b680a307adff | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Jul 03 10:13:21 2016 -0400 |
| committer | David Benjamin <davidben@google.com> | Wed Jul 06 23:15:17 2016 +0000 |
| tree | 88b3c473bf234fb958dbbf1be629efe6b57bcf6f | |
| parent | 45a8c8a3c4e1132989471a80518b15230ac93de5 [diff] |
Convert test_mod_exp_mont5 test vectors. These were generated by running test_mod_exp_mont5 10 times. The values with Montgomery representation 1 were generated separately so the test file could preserve the comment. (Though, at 10,000 lines, no one's going to find it...) BUG=31 Change-Id: I8e9d4d6d7b5f7d283bd259df10a1dbdc90b888cf Reviewed-on: https://boringssl-review.googlesource.com/8611 Reviewed-by: David Benjamin <davidben@google.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
There are other files in this directory which might be helpful: