Google Git
Sign in
boringssl / boringssl.git / refs/tags/fips-20210429
tag2c45d4e03e35a2dd73834252e11e8a7282eb9185
taggerAdam Langley <agl@google.com>Thu Jun 24 14:21:45 2021 -0700
object853ca1ea1168dff08011e5d42d94609cc0ca2e27 
fips-20210429
commit853ca1ea1168dff08011e5d42d94609cc0ca2e27[log] [tgz]
authorAdam Langley <alangley@gmail.com>Thu Apr 29 16:37:37 2021 -0700
committerAdam Langley <agl@google.com>Fri Apr 30 16:26:57 2021 +0000
tree2f185dd89fd0f74e73254ff861849fa3ccabdf8c
parentd4f877ea3c16cd6b3c2b7071b427aff6af2ae345 [diff]
Remove non-deterministic bits from ECDSA ACVP test.

When updating the test file for SHA-1 support, I forgot to remove the
non-deterministic bits (i.e. key and signature generation) from the
input vectors.

Change-Id: Id47f9b2cc85282f68b71aedc271d4b4b53e04c70
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/47285
Reviewed-by: David Benjamin <davidben@google.com>
2 files changed
tree: 2f185dd89fd0f74e73254ff861849fa3ccabdf8c
  1. .github/
  2. crypto/
  3. decrepit/
  4. fuzz/
  5. include/
  6. ssl/
  7. third_party/
  8. tool/
  9. util/
  10. .clang-format
  11. .gitignore
  12. API-CONVENTIONS.md
  13. BREAKING-CHANGES.md
  14. BUILDING.md
  15. CMakeLists.txt
  16. codereview.settings
  17. CONTRIBUTING.md
  18. FUZZING.md
  19. go.mod
  20. go.sum
  21. INCORPORATING.md
  22. LICENSE
  23. PORTING.md
  24. README.md
  25. SANDBOXING.md
  26. sources.cmake
  27. STYLE.md
README.md

BoringSSL

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.

Project links:

There are other files in this directory which might be helpful: