| commit | 6e20b77e6b79069e2468686bdc69169d3fa2252e | [log] [tgz] |
|---|---|---|
| author | Bob Beck <bbe@google.com> | Wed Feb 08 11:32:19 2023 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 08 19:04:21 2023 +0000 |
| tree | f721b90bea0194732329cdc5b9f6ee53b83f75b2 | |
| parent | 19721cd7789e4e4a69c0786951b452262eaba251 [diff] |
Get rid of time_t usage internally, change to int64_t We still keep time_t stuff around for calling time() and for external interfaces that are meant to give you time_t values, but we stop using time_t internally. For publicly exposed and used inputs that rely on time_t, _posix versions are added to support providing times as an int64_t, and internal use is changed to use the _posix version. Several legacy functions which are extensivly used and and use pointers to time_t are retained for compatibility, along with posix time versions of them which we use exclusively. This fixes the tests which were disabled on 32 bit platorms to always run. Update-Note: This is a potentially breaking change for things that bind to the ASN1_[UTC|GENERALIZED]TIME_set and ASN1_TIME_adj family of functions (and can not type convert a time_t to an int64). Bug: 416 Change-Id: Ic4daba5a299d8f35191853742640750a1ecc53d6 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54765 Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: 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: