| commit | c9a7dd687987666df5910f2b35fdc8c3d1e5ed05 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Mar 19 18:46:57 2022 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 25 16:19:16 2022 +0000 |
| tree | 615e67f649bcf127981b3d3a41f709b50c9a9d70 | |
| parent | 4984e4a6325e9c6302f846c7bf2b75e8ea3fd9dd [diff] |
Retire the Windows BIO_printf workaround. With the UCRT, introduced in VS 2015, vsnprintf in MSVC is now C99-conformant. See: https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/vsnprintf-vsnprintf-vsnprintf-l-vsnwprintf-vsnwprintf-l?view=msvc-170 It is a little unclear to me whether "Beginning with the UCRT in Visual Studio 2015 and Windows 10" means it is only C99-conformant in Windows 10, or if this is referring to how the UCRT starts becoming an OS component in Windows 10. I think the latter. This document talks about the UCRT: https://docs.microsoft.com/en-us/cpp/porting/upgrade-your-code-to-the-universal-crt?view=msvc-170 But we have tests which cover this in BIOTest.Printf. If it's not C99-compliant in Windows 7, we'll notice in Chromium's CI. Change-Id: I932ec2633f94bd77dbe797b06a6bfbc95a568335 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/52086 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@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: