Don't bother checking for NULL pointers in AES key schedule assembly

Some of the AES implementations tried to cleanly check for NULL input
and output pointers, but others did not, so callers could not rely on

(If we end up needing to check this for some reason, we should do it in
the C wrapper.)

Change-Id: I495e5b3689837242b5c51bf01840997845190754
Reviewed-by: Bob Beck <>
Commit-Queue: David Benjamin <>
13 files changed
tree: 0f9bf918d0be79198d42c9d23f7d69aed7b09460
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. gen/
  7. include/
  8. pki/
  9. rust/
  10. ssl/
  11. third_party/
  12. tool/
  13. util/
  14. .bazelignore
  15. .bazelrc
  16. .clang-format
  17. .gitignore
  20. BUILD.bazel
  21. build.json
  23. CMakeLists.txt
  24. codereview.settings
  27. go.mod
  28. go.sum
  31. MODULE.bazel
  32. MODULE.bazel.lock
  34. PrivacyInfo.xcprivacy


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: