| commit | cba7adcd108e9a41a992b4c4fc18b050e4d05a66 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Jan 20 09:55:50 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 25 23:35:33 2024 +0000 |
| tree | bd4aefec2e212ae42291385cd243ca07c5f049e3 | |
| parent | 7f45053d42ae0b5f4d5d96fa471d671c6d1462e9 [diff] |
Move single-use macros from internal.h to des.c These macros are unnamespaced and only used in one file. Keep their definitions more local. Also remove the #undefs at the end of des.c. They date to when des.c was part of bcm.c, but it isn't anymore. Change-Id: I6306929929f2304b93c3fdb2e787965c40729d6a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65688 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: 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: