Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update BoringSSL from Chromium 87.0.4280.142 #2251

Merged
merged 4 commits into from
Jan 22, 2024

Conversation

dahlstrom-g
Copy link
Contributor

b/309016038

chrome-release-bot and others added 2 commits January 18, 2024 18:00
git-subtree-dir: third_party/boringssl
git-subtree-split: f73da6d3eaeb33e9d4bcb497bf13c655143a82f9
This was introduced in OpenSSL 1.1.1, and wpa_supplicant expects us to
have it. We had this same function as SSL_CIPHER_get_value (to match
SSL_get_cipher_by_value). Align with upstream's name.

It seems we also had a ssl_cipher_get_value lying around, so fold them
together. (I've retained the assert in ssl_cipher_get_value as it seems
reasonable enough; casting a hypothetical SSLv2 cipher ID to uint16_t
would not behave correctly.)

Change-Id: Ifbec460435bbc483f2c3de988522e321f2708172
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/42966
Commit-Queue: Adam Langley <[email protected]>
Reviewed-by: Adam Langley <[email protected]>
git-subtree-dir: third_party/boringssl/src
git-subtree-split: 3743aafdacff2f7b083615a043a37101f740fa53
@dahlstrom-g dahlstrom-g force-pushed the boringssl-87.0.4280.142 branch 2 times, most recently from 9eca3ae to 61a0194 Compare January 19, 2024 22:00
@dahlstrom-g dahlstrom-g force-pushed the boringssl-87.0.4280.142 branch 2 times, most recently from 4bd1dd0 to 2101749 Compare January 20, 2024 02:00
@dahlstrom-g dahlstrom-g force-pushed the boringssl-87.0.4280.142 branch from 2101749 to 78c8bca Compare January 21, 2024 02:00
@dahlstrom-g dahlstrom-g merged commit 194af8f into youtube:main Jan 22, 2024
322 of 330 checks passed
@dahlstrom-g dahlstrom-g deleted the boringssl-87.0.4280.142 branch January 22, 2024 05:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants