Remove NewZeroed entirely NewZeroed was never actually necessary. We were performing value-initialization, which means that, if the default constructor were not user-provided, it does zero-initialization anyway. If the default constructor is user-provided, this changes and the user-provided constructor is responsible for initializing every field. NewZeroed looks like it saved this case, but it does not according to GCC. GCC believes that, for all types, a memset preceding a placement new can be deleted. Thus we can simply replace NewZeroed with New. We need to be very careful that, when we introduce a constructor to a type, we initialize the fields explicitly. This was always true in C++. Bug: 491512320 Change-Id: I8f7cba6afaffeb8baf5f1190c2f7590bfd459b0a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/90667 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Rudolf Polzer <rpolzer@google.com> Commit-Queue: Rudolf Polzer <rpolzer@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:
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: