| commit | bfcab2aa518899ce71e7ffbc23bb22c4ef51858f | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun May 12 10:26:48 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 21 19:55:13 2024 +0000 |
| tree | acfb4aaee05d022f1b29abeb98eba43a6195b136 | |
| parent | 68c29a24ee6c9c70ecce56766ca70b115aad768f [diff] |
Use SEH directives for aes_hw_set_encrypt_key and aes_hw_set_decrypt_key These functions don't use the calling convention conversion, so we can use the automatic things. This will make it a little easier, in the commit, to split these into a few functions. Note this only works because aes_hw_set_encrypt_key and aes_hw_set_decrypt_key are the last two functions in this file. We cannot interleave automatic and handwritten SEH tables. This also lets us remove some hand-encoded instructions. When OpenSSL handwrites SEH tables, they had to hand-encode instructions just in case the assembler picked a different length encoding. The synthesized tables fill in computed offsets. Bug: 259 Change-Id: Ic94cdceeab1378ef7afb217de7643a6bb75ae1a2 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/68687 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: Bob Beck <bbe@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.
Project links:
There are other files in this directory which might be helpful: