Google Git
Sign in
boringssl / boringssl / 803062a053a86cff4ef1ffac90d12a82885688f3
commit803062a053a86cff4ef1ffac90d12a82885688f3[log] [tgz]
authorDaniel McCarney <daniel@binaryparadox.net>Tue Dec 17 16:49:16 2024 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jan 08 09:54:19 2025 -0800
tree5f7bbda58c2e8cb3aa30d6b1566ffa6c00d216f3
parentaf821e7c650739d6466948981b42094737533978 [diff]
util/fipstools: document AES-gcm-randnonce cmds

The acvptool supports modules that have an ACVP-AES-GCM algorithm
capability that includes ivGen=internal. For these test vectors
the tool invokes the AES-GCM-randnonce/open and AES-GCM-randnonce/seal
commands.

This commit updates ACVP.md to describe these commands since their
arguments differ slightly from the base AES-GCM/open and AES-GCM/seal
commands used for ivGen=external vectors.

Change-Id: I52d84e2cc721adf1e1d8314b2679db4896f000b4
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/74527
Reviewed-by: Bob Beck <bbe@google.com>
Commit-Queue: Adam Langley <agl@google.com>
Reviewed-by: Adam Langley <agl@google.com>
1 file changed
tree: 5f7bbda58c2e8cb3aa30d6b1566ffa6c00d216f3
  1. .bcr/
  2. .github/
  3. cmake/
  4. crypto/
  5. decrepit/
  6. docs/
  7. fuzz/
  8. gen/
  9. include/
  10. infra/
  11. pki/
  12. rust/
  13. ssl/
  14. third_party/
  15. tool/
  16. util/
  17. .bazelignore
  18. .bazelrc
  19. .bazelversion
  20. .clang-format
  21. .gitignore
  22. API-CONVENTIONS.md
  23. AUTHORS
  24. BREAKING-CHANGES.md
  25. BUILD.bazel
  26. build.json
  27. BUILDING.md
  28. CMakeLists.txt
  29. codereview.settings
  30. CONTRIBUTING.md
  31. FUZZING.md
  32. go.mod
  33. go.sum
  34. INCORPORATING.md
  35. LICENSE
  36. MODULE.bazel
  37. MODULE.bazel.lock
  38. PORTING.md
  39. PrivacyInfo.xcprivacy
  40. README.md
  41. SANDBOXING.md
  42. 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:

To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.

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