| commit | 85145fdc914b4c01b9bb16a9253067958e327283 | [log] [tgz] |
|---|---|---|
| author | Daniel Verkamp <dverkamp@google.com> | Tue Apr 08 12:30:20 2025 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 23 10:56:42 2025 -0700 |
| tree | 41a83d5afcbd8944559e7420eaee18e354ccdaf0 | |
| parent | 8d312a04845e98a0c3ceafde50377b56fc83d2c0 [diff] |
Replace sscanf() with strtoull() in OPENSSL_ia32cap parser This simplifies the code a bit while still accepting the same syntax as previously: decimal or hexadecimal (hex must be prefixed with exactly "0x", case sensitive), potentially clearing the corresponding bits if prefixed with "~". An explicit base (either 10 or 16) is passed to strtoull() to ensure that zero-prefixed decimal numbers are not parsed as octal. As a side effect, this also avoids the stdio dependency, which is helpful for bare-metal environments. Change-Id: I2b250161eb154c5e0bbc7629b695f573f4b21733 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/78367 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@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: