Age | Commit message (Collapse) | Author |
|
am: 8e53732cc1
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/18978268
Change-Id: I2fa3df19f25aca28fe00a802889a0873fa5fefef
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Change-Id: Ibe2e0dc06748b4e01ec7428647f8b42fed40fb91
|
|
*** Notes for Cherry-Pick to tm-dev:
See b/233873228#comment10 for the reasoning behind this late breaking change.
This change needs to go into tm-dev before FRC to ensure libcrypto in /system is built from the version we certify.
The FRC module train is due to be completely respun next week so it will also go into the FCS modules version of libcrypto. *However* as there are no API, ABI, functional or test expectation changes there is no urgency to getting the change into the Mainline train, so we just need to ensure all modules that bundle libcrypto board a Mainline train before the certification process moves on to NIST evaluation.
*** Original change description follows
Final FIPS changes for 2022.
The upstream branch being merged contains cherry-picks of
changes needed for FIPS certification plus a couple of critical
bug fixes. No API or ABI changes. No functional changes.
Those changes are also in the main upstream branch, so won't
be overwritten by the next routine rollup with do using our
UPDATING script.
Includes the following changes:
* Add an extra reduction step to the end of RSAZ.
* Always end BN_mod_exp_mont_consttime with normal Montgomery
reduction.
* More includes for builds that don't use bcm.c
* Add some more includes.
* Increase ACVP sizes.
* Move digestsign.c into the module.
Bug: 233873228
Test: atest CtsLibcoreTestCases CtsLibcoreOkHttpTestCases
Change-Id: I1d41a5d6f51af818253b55b8b99e0e73ea6e24ba
Merged-In: I1d41a5d6f51af818253b55b8b99e0e73ea6e24ba
(cherry picked from commit abd455b494b016109d2bfd1ca7a29619fb4c35a3)
|
|
am: 787ef00560
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/18720980
Change-Id: I21d7dd5adea18fbb24d2c15217053a04d47d3037
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Change-Id: I298e63ccfa0bad34ba420c1aa2184a7392ece3ee
|
|
Cherry-pick note: Needs to go into tm-dev base OS for FIPS certification
(b/233873228) and into the July module train to prevent breaking ABN Amro banking app in .nl (b/231880827) so cp-ing into tm-dev where it will merge forward into all needed branches.
This includes the following changes:
https://boringssl.googlesource.com/boringssl/+log/c9a7dd687987666df5910f2b35fdc8c3d1e5ed05..1530333b25589ee4d4d52b10e78ee55dd82f6dcd
* Remove X509_CRL_METHOD.
Update-Note: APIs relating to X509_CRL_METHOD are removed.
* Clean up ECDSA EVP_PKEY_CTRL_MD validation.
* Add a service indicator for FIPS 140-3.
* Move cmac into the FIPS module boundary.
* Use CMake's C/C++ version features.
* Update build tools.
* Don't leave stray errors in the error queue in X509_print_ex.
* Switch to the CIPD version of CMake on Windows.
* limit the feature macro stuff to __linux__
* Enforce X.509 version invariants more consistently.
Update-Note: Invalid CRL and CSR versions will no longer be accepted.
X509_set_version, etc., no longer allow invalid versions.
* Remove X509_to_X509_REQ.
Update-Note: Removed seemingly unused public API.
* Declare EVP_AEAD_CTX in base.h, like other typedefs.
* Add missing blank line between functions.
* Remove unions in EC_SCALAR and EC_FELEM.
* Implement SSL_CTX_set_num_tickets.
* Add tests for X509_NAME_print_ex.
* acvp: test CTR-DRBG with reseed in modulewrapper.
* Do pending `go fmt` updates.
* acvp: test SHA-512/256 with HMAC, RSA (PSS), and ECDSA.
* Add PSS to the AVCP regcap.
* Drop ACVP support for 3DES.
* Add function to return the name of the FIPS module.
* Support running tests on non-NEON devices.
* Update delocate tests
* Tidy up how ASN1_STRING_print_ex figures out the type.
* Remove the ASN1_TLC cache. It appears to not help performance.
* Fix build for older CMake versions.
* Remove code added to avoid SHA1 weakness.
* Update comment in light of prior change.
* ChaCha20-Poly1305 for Armv8 (AArch64)
* Replace the last strcasecmp with OPENSSL_strcasecmp.
* [build] Fix build with HEAD clang.
* Make calls to the verify callback consistant by calling ctx->verify_cb directly. This removes some temporary variables that would only be used to hold ctx->verify_cb.
* Try to require C11 (in non-MSVC compilers).
Update-Note: If the build fails with an error about C11, remove -std=c99
or -std=gnu99 from your build. Refcounting will get faster.
* Try to require C++14.
Update-Note: C++14 is now required to build BoringSSL. If the build
breaks, make sure your compiler is C++14-capable and is not passing
-std=c++11. If this is causing problems for your project, let us know.
* Reject [UNIVERSAL 0] in DER/BER element parsers.
Update-Note: There are two kinds of impacts I might expect from this
change. The first is BER parsers might be relying on the CBS DER/BER
element parser to pick up EOCs, as our ber.c does. This should be caught
by the most basic unit test and can be fixed by detecting EOCs
externally.
* Add CMake install rules.
* P-256 assembly optimisations for Aarch64.
* hrss: always normalize.
* Use SHA-256 for the FIPS integrity check everywhere.
* Remove unused variable
* Use X509 certificate alias as friendlyName in PKCS12
Bug: 231880827
Bug: 233873228
Test: atest CtsLibcoreTestCases CtsLibcoreOkHttpTestCases
Change-Id: I748d8d55ffab4ea4441648307a797e7b709b6def
(cherry picked from commit e6e9a5d015a010d2fab0a13392eca548f7c370cc)
Merged-In: I748d8d55ffab4ea4441648307a797e7b709b6def
|
|
Change-Id: Ia5b36255b8ef8aac224d24396a5ccf1e09f3c708
|
|
Change-Id: I12b454241c456aaf49df22e8c1cf353aa1b9deb7
|
|
Maintains pre-Android 13 behaviour by ensuring any crypto
module failures are detected at boot time.
For the libcrypto in /system this may not be needed and
we can change the behaviour later.
For libcrypto in the Conscrypt APEX, this is needed to maintain
current behaviour on older releases.
Bug: 231946889
Test: Flash and boot.
Change-Id: I7dee7f0bf953ea2c5026881d5acc13698de0626d
(cherry picked from commit c90762593f6490df8f6b13020d91e3466892b106)
Merged-In: I7dee7f0bf953ea2c5026881d5acc13698de0626d
|
|
am: 8e186edca5
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17898398
Change-Id: Icf7a0e8be36d0d27e7ab8bf4e2db3c5ed8fc831c
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Change-Id: If4a3ffe95bb8c430dfcd3ad665ceb401624a0dfd
|
|
into tm-dev
* changes:
[automerged blank] [DO NOT MERGE] Don't loop forever in BN_mod_sqrt on invalid inputs. 2p: 43ca36f693
[DO NOT MERGE] Don't loop forever in BN_mod_sqrt on invalid inputs.
|
|
am: 1596db9f7a
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17875914
Change-Id: I61ffcf0486c2872ae20b414c933c599cc7e54216
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Change-Id: Id9a5f8449d88e4611f001cdf26f27629080b5ca8
|
|
sc-v2-dev-plus-aosp-without-vendor@8433047 am: e24b7a1f5d -s ours am: c79cf04f4d -s ours
am skip reason: Merged-In Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd with SHA-1 6d77d67fee is already in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17805470
Change-Id: I1f2beb67e10ce5121fdf534ebcfc144e077c5876
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
sc-v2-dev-plus-aosp-without-vendor@8433047 am: e24b7a1f5d -s ours
am skip reason: Merged-In Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd with SHA-1 6d77d67fee is already in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17805470
Change-Id: I5d7f0b310d059af0fc4ed387ec570c24eba52334
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Bug: 226662282
Merged-In: Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd
Change-Id: Ie5c7bf77014b4b85b60c0ef373165936b4e1f566
|
|
invalid inputs. 2p: 43ca36f693
Blank merge reason: commit message contains skip directive
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17745127
Bug: 224813912
Change-Id: Ib9d36933b408a67b3f1677d06da8b8bb424ccf7c
|
|
Cherry-picked from
https://boringssl-review.googlesource.com/c/boringssl/+/51925
to fix CVE-2022-0778. Should not be merged downstream as
it already exists in a rollup BoringSSL CL there.
Upstream commit message follows:-
BN_mod_sqrt implements the Tonelli–Shanks algorithm, which requires a
prime modulus. It was written such that, given a composite modulus, it
would sometimes loop forever. This change fixes the algorithm to always
terminate. However, callers must still pass a prime modulus for the
function to have a defined output.
In OpenSSL, this loop resulted in a DoS vulnerability, CVE-2022-0778.
BoringSSL is mostly unaffected by this. In particular, this case is not
reachable in BoringSSL from certificate and other ASN.1 elliptic curve
parsing code. Any impact in BoringSSL is limited to:
- Callers of EC_GROUP_new_curve_GFp that take untrusted curve parameters
- Callers of BN_mod_sqrt that take untrusted moduli
This CL updates documentation of those functions to clarify that callers
should not pass attacker-controlled values. Even with the infinite loop
fixed, doing so breaks preconditions and will give undefined output.
Bug: 224813912
Test: TH
Change-Id: I64dc1220aaaaafedba02d2ac0e4232a3a0648160
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/51925
Reviewed-by: Adam Langley <agl@google.com>
Reviewed-by: Martin Kreichgauer <martinkr@google.com>
Commit-Queue: Adam Langley <agl@google.com>
|
|
am: 71c968b9c9
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17731311
Change-Id: Icf19786e23b7923eea8bdc88853daa5f03086d35
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Change-Id: I0aa640e6704b8d4b6d4a57db859fabe86ed3d358
|
|
am: 67506730c7 am: 9ff3c15dd7
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/2061407
Change-Id: I015e36bc118c8424ca32a0af184ada2bcf641038
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
am: 67506730c7
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/2061407
Change-Id: Ia2c3f80962d1c77feff883d4f0bf063202054238
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/2061407
Change-Id: I612d2626f43bd76efad81237d9757062ef96f14b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
am: c3260fde70
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17698922
Change-Id: I4813c3609019d0fa300f17d37689cc248affd0c5
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Change-Id: I33546a1faf84d62ae61ccbe0c754855d82a898a9
|
|
The tests run from /data/local/tmp and likely to pick up
libraries from the sustem partition (or not in some libssl cases)
rather than the APEX.
Fixes: 228778981
Test: atest boringssl_crypto_tests boringssl_ssl_tests
Change-Id: I0429686a87723447179a6cf32c6f9d4f1a7e7fc1
|
|
c9a7dd687987666df5910f2b35fdc8c3d1e5ed05." am: ea823ff68d -s ours am: 04b0aa0916 -s ours am: 1c4c54db07 -s ours
am skip reason: Merged-In Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd with SHA-1 6d77d67fee is already in history
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/2046663
Change-Id: I6687811378faace1d6ac6cc47885c7888d9f11c7
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
c9a7dd687987666df5910f2b35fdc8c3d1e5ed05. am: b439634923 -s ours am: 7ef1fe2744 -s ours am: b49eb35cb9 -s ours
am skip reason: Merged-In Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd with SHA-1 6d77d67fee is already in history
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/2046663
Change-Id: Ia594a48f0e4737d05be96e17137e88759256aa07
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
c9a7dd687987666df5910f2b35fdc8c3d1e5ed05." am: ea823ff68d -s ours am: 04b0aa0916 -s ours
am skip reason: Merged-In Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd with SHA-1 6d77d67fee is already in history
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/2046663
Change-Id: I9f47227830de55a9277f1ee91f9c1747b1f84940
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
c9a7dd687987666df5910f2b35fdc8c3d1e5ed05. am: b439634923 -s ours am: 7ef1fe2744 -s ours
am skip reason: Merged-In Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd with SHA-1 6d77d67fee is already in history
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/2046663
Change-Id: Ia0f2890b9789ac1a8a3e5d1404772b151f419ab6
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
c9a7dd687987666df5910f2b35fdc8c3d1e5ed05." am: ea823ff68d -s ours
am skip reason: Merged-In Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd with SHA-1 6d77d67fee is already in history
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/2046663
Change-Id: Ic3d224bfee238e8ac78fda278c2aa76c5e5491e0
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
c9a7dd687987666df5910f2b35fdc8c3d1e5ed05. am: b439634923 -s ours
am skip reason: Merged-In Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd with SHA-1 6d77d67fee is already in history
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/2046663
Change-Id: I1ee21e2f328a897085028fe4a4394ab9d7fba847
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
am: 71cfb486a8
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17671077
Change-Id: I2d714924b839456866299e55151180f4adaba6f5
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Change-Id: I858027f742dc7225993c224337b2521c3d920f0e
|
|
6d77d67fee am: d3915051ff
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17654895
Change-Id: Id948d1017ae1d0dc90bc3c195585ecede94501e5
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
6d77d67fee
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17654895
Change-Id: I5d2e75dbf9ad258221881ee73a80aad924e0676e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Cherry-picked from https://r.android.com/2046663 to prevent merge conflicts and http://ag/17606941 because the original CP was to the wrong branch.
This includes the following changes:
https://boringssl.googlesource.com/boringssl/+log/81502beeddc5f116d44d0898c6c4a33057198db8..c9a7dd687987666df5910f2b35fdc8c3d1e5ed05
* Retire the Windows BIO_printf workaround.
* Work around another C language bug with empty spans.
* ASAN replaces malloc and free with its own implementation.
* Update fiat-crypto.
* Remove VS 2015 support.
Update-Note: BoringSSL may no longer build with VS 2015. Consumers
should upgrade to the latest Visual Studio release. VS 2017 or later is
required.
* Remove X509_TRUST_set_default.
* Replace internal use sha1 hash with sha256.
* Document that |EC_KEY_generate_fips| works for both cases.
* Allow the integrity test to be run on demand.
* Add a function to return a FIPS version.
* Add a function to tell if an algorithm is FIPS approved.
* Add vs2019 to vs_toolchain.py.
* Unexport X509_CERT_AUX and remove X509_CERT_AUX.other
* Document and tidy up X509_alias_get0, etc.
* Don't loop forever in BN_mod_sqrt on invalid inputs.
* Make a whitespace commit to trigger a build.
* Rust bindings: Use CARGO_MANIFEST_DIR in build.rs
* Remove ASN1_ADB_INTEGER.
* Replace an ASN1_INTEGER_get call with ASN1_INTEGER_get_uint64
* Correctly handle LONG_MIN in ASN1_INTEGER_get.
* Implement ASN1_INTEGER_set_uint64 with ASN1_STRING_set.
* Rewrite and tighten ASN1_INTEGER encoding and decoding.
Update-Note: Invalid INTEGERs will no longer parse, but they already
would not have parsed in OpenSSL. Additionally, zero is now internally
represented as "" rather than "\0".
* Deduplicate the rest of ASN1_INTEGER and ASN1_ENUMERATED.
Update-Note: ASN1_INTEGER_to_BN and ASN1_ENUMERATED_to_BN will now fail
when called on an ASN1_STRING/ASN1_INTEGER/ASN1_ENUMERATED (they're all
the same type) with the wrong runtime type value. Previously, callers
that mixed them up would get the right answer on positive values and
silently misinterpret the input on negative values. This change matches
OpenSSL's 1.1.0's behavior.
* Fix theoretical overflow in ASN1_INTEGER_cmp.
* Include rsa/internal.h for |...no_self_test| functions.
* Limit the pthread_rwlock workaround to glibc.
Update-Note: If there are non-glibc libcs with similarly problematic
headers, this may break the build. Let us know if it does.
* Rewrite ASN1_INTEGER tests.
* Use X509V3_add_value_int in i2v_AUTHORITY_KEYID.
* Fix x509v3_bytes_to_hex when passed the empty string.
* Reimplement ASN1_get_object with CBS.
Update-Note: Invalid certificates (and the few external structures using
asn1t.h) with incorrectly-encoded tags will now be rejected.
* Add an explicit indefinite-length output to CBS_get_any_ber_asn1_element.
Update-Note: This is a breaking change to CBS_get_any_ber_asn1_element.
There is only one external caller of this function, and it should be
possible to fix them atomically with this change, so I haven't bothered
introducing another name, etc. (See cl/429632075 for the fix.)
* Use ctype(3) in a more standards-conformant way.
Bug: 160351635
Test: atest CtsLibcoreTestCases CtsLibcoreOkHttpTestCases
Change-Id: Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd
(cherry picked from commit 1ffe10415b506d2f2336a3249368c7b5f6b788e9)
|
|
am: 0c926c75f2
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/1749846
Change-Id: I50a559f417648f9b76d2d2b8c66f81a3acf31f9d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/1749846
Change-Id: Ife14eb824f142fd1d7d017c421ee75a625eb1d27
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/external/boringssl/+/1749846
Change-Id: I2d27efae84eb87374874bddbf5c2b3507ab19889
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
This includes the following changes:
https://boringssl.googlesource.com/boringssl/+log/81502beeddc5f116d44d0898c6c4a33057198db8..c9a7dd687987666df5910f2b35fdc8c3d1e5ed05
* Retire the Windows BIO_printf workaround.
* Work around another C language bug with empty spans.
* ASAN replaces malloc and free with its own implementation.
* Update fiat-crypto.
* Remove VS 2015 support.
Update-Note: BoringSSL may no longer build with VS 2015. Consumers
should upgrade to the latest Visual Studio release. VS 2017 or later is
required.
* Remove X509_TRUST_set_default.
* Replace internal use sha1 hash with sha256.
* Document that |EC_KEY_generate_fips| works for both cases.
* Allow the integrity test to be run on demand.
* Add a function to return a FIPS version.
* Add a function to tell if an algorithm is FIPS approved.
* Add vs2019 to vs_toolchain.py.
* Unexport X509_CERT_AUX and remove X509_CERT_AUX.other
* Document and tidy up X509_alias_get0, etc.
* Don't loop forever in BN_mod_sqrt on invalid inputs.
* Make a whitespace commit to trigger a build.
* Rust bindings: Use CARGO_MANIFEST_DIR in build.rs
* Remove ASN1_ADB_INTEGER.
* Replace an ASN1_INTEGER_get call with ASN1_INTEGER_get_uint64
* Correctly handle LONG_MIN in ASN1_INTEGER_get.
* Implement ASN1_INTEGER_set_uint64 with ASN1_STRING_set.
* Rewrite and tighten ASN1_INTEGER encoding and decoding.
Update-Note: Invalid INTEGERs will no longer parse, but they already
would not have parsed in OpenSSL. Additionally, zero is now internally
represented as "" rather than "\0".
* Deduplicate the rest of ASN1_INTEGER and ASN1_ENUMERATED.
Update-Note: ASN1_INTEGER_to_BN and ASN1_ENUMERATED_to_BN will now fail
when called on an ASN1_STRING/ASN1_INTEGER/ASN1_ENUMERATED (they're all
the same type) with the wrong runtime type value. Previously, callers
that mixed them up would get the right answer on positive values and
silently misinterpret the input on negative values. This change matches
OpenSSL's 1.1.0's behavior.
* Fix theoretical overflow in ASN1_INTEGER_cmp.
* Include rsa/internal.h for |...no_self_test| functions.
* Limit the pthread_rwlock workaround to glibc.
Update-Note: If there are non-glibc libcs with similarly problematic
headers, this may break the build. Let us know if it does.
* Rewrite ASN1_INTEGER tests.
* Use X509V3_add_value_int in i2v_AUTHORITY_KEYID.
* Fix x509v3_bytes_to_hex when passed the empty string.
* Reimplement ASN1_get_object with CBS.
Update-Note: Invalid certificates (and the few external structures using
asn1t.h) with incorrectly-encoded tags will now be rejected.
* Add an explicit indefinite-length output to CBS_get_any_ber_asn1_element.
Update-Note: This is a breaking change to CBS_get_any_ber_asn1_element.
There is only one external caller of this function, and it should be
possible to fix them atomically with this change, so I haven't bothered
introducing another name, etc. (See cl/429632075 for the fix.)
* Use ctype(3) in a more standards-conformant way.
Bug: 160351635
Test: atest CtsLibcoreTestCases CtsLibcoreOkHttpTestCases
Change-Id: Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd
Merged-In: Iffd9451788b67d3da80cefbcf8d3d0ffb7d682fd
|
|
Bug: 187236336
Bug: 192368160
Test: mts-tradefed run mts-conscrypt
Change-Id: I8b0dd685ad0db477e41dab395489fe42e70a4fe1
|
|
am: 6c1a82fbe7
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17563783
Change-Id: Icf79139d35f894deb826d9faf0a26ac46fd71ad9
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Change-Id: I2b4f1de182f6df21f8f51f5c69d2c6f200e87bdb
|
|
am: c3df2ddaeb -s ours
am skip reason: Merged-In Ic67ad4214f6feb67a9e95410b16cf3e096cc0627 with SHA-1 1159a80f83 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17545244
Change-Id: Id19cef4cd35f54b698623d38c79602c896972e5d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
am skip reason: Merged-In Ic67ad4214f6feb67a9e95410b16cf3e096cc0627 with SHA-1 1159a80f83 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/boringssl/+/17545244
Change-Id: I723ea76c972a9bfaa6b4a7a30c9e30d6ef741e12
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Bug: 226662282
Merged-In: Ic67ad4214f6feb67a9e95410b16cf3e096cc0627
Change-Id: I1ee06676dc15d76f044b3129c4cb73877e9b1187
|
|
Change-Id: Idbf955b1bd5ad1079b0c72ee45264d8d55f0fb9e
|