apolcyn
5378a327b4
[boringssl] Update boringssl version ( #37631 )
...
Generated by release script
Closes #37631
PiperOrigin-RevId: 672589621
3 months ago
AJ Heller
b81f754a29
[BoringSSL] Update third_party/boringssl-with-bazel ( #37223 )
...
Change was created by the release automation script. See go/grpc-release.
Closes #37223
PiperOrigin-RevId: 652942434
5 months ago
Xuan Wang
ecdb5caf83
[BoringSSL] Update third_party/boringssl-with-bazel ( #36716 )
...
Change was created by the release automation script. See go/grpc-release.
Closes #36716
PiperOrigin-RevId: 638337588
6 months ago
Yash Tibrewal
a0bee78a28
[BoringSSL] Update third_party/boringssl-with-bazel ( #36435 )
...
Change was created by the release automation script. See go/grpc-release.
Closes #36435
PiperOrigin-RevId: 629574967
7 months ago
Xuan Wang
0f77a5ad9e
[BoringSSL] Update third_party/boringssl-with-bazel ( #36089 )
...
Change was created by the release automation script. See go/grpc-release.
Additional Changes:
* Boring SSL started to [Require SSE2 when targetting 32-bit x86](56d3ad9d23
), thus added `-msse2` to fix some build failures.
Closes #36089
PiperOrigin-RevId: 614822548
9 months ago
Eugene Ostroukhov
239399212a
[BoringSSL] "Revert Update third_party/boringssl-with-bazel ( #35842 )" ( #35847 )
...
This reverts commit c968d1a56a
.
Closes #35847
PiperOrigin-RevId: 605117622
10 months ago
Eugene Ostroukhov
c968d1a56a
[BoringSSL] Update third_party/boringssl-with-bazel ( #35842 )
...
Closes #35842
PiperOrigin-RevId: 605091673
10 months ago
Eugene Ostroukhov
038215b504
[BoringSSL] Revert "Update third_party/boringssl-with-bazel ( #35811 )" ( #35834 )
...
This reverts commit c2a2e8c09d
.
Closes #35834
PiperOrigin-RevId: 604800979
10 months ago
Eugene Ostroukhov
c2a2e8c09d
[BoringSSL] Update third_party/boringssl-with-bazel ( #35811 )
...
Change was created by the release automation script. See go/grpc-release.
Closes #35811
PiperOrigin-RevId: 604701943
10 months ago
Esun Kim
1f979d2a83
[BoringSSL] Update third_party/boringssl-with-bazel ( #35768 )
...
Change was created by the release automation script. See go/grpc-release.
On top of changes made by the script, `setup.py` had to be updated to have `/std:c11` option for MSVC to use c11 features for boringssl.
Closes #35768
PiperOrigin-RevId: 603403329
10 months ago
Esun Kim
650c2ea492
[Deps] Update boringssl 202308211007 ( #34115 )
...
Part of gRPC release
1 year ago
AJ Heller
5e3fe08f37
[BoringSSL] Update third_party/boringssl-with-bazel ( #33690 )
...
Change was created by the release automation script. See go/grpc-release
1 year ago
Sergii Tkachenko
de6ed9ba9f
[Python] Migrate from yapf to black ( #33138 )
...
- Switched from yapf to black
- Reconfigure isort for black
- Resolve black/pylint idiosyncrasies
Note: I used `--experimental-string-processing` because black was
producing "implicit string concatenation", similar to what described
here: https://github.com/psf/black/issues/1837 . While currently this
feature is experimental, it will be enabled by default:
https://github.com/psf/black/issues/2188 . After running black with the
new string processing so that the generated code merges these `"hello" "
world"` strings concatenations, then I removed
`--experimental-string-processing` for stability, and regenerated the
code again.
To the reviewer: don't even try to open "Files Changed" tab 😄 It's
better to review commit-by-commit, and ignore `run black and isort`.
1 year ago
Yijie Ma
004ddbea90
[BoringSSL] Update third_party/boringssl-with-bazel ( #33150 )
...
Change was created by the release automation script. See go/grpc-release
2 years ago
Yash Tibrewal
b454d2d474
[BoringSSL] Update third_party/boringssl-with-bazel ( #32868 )
...
Change was created by the release automation script. See go/grpc-release
2 years ago
Stanley Cheung
39780ba2b5
Update third_party/boringssl-with-bazel ( #32721 )
...
Change was created by the release automation script. See
go/grpc-release.
2 years ago
Jan Tattermusch
9c45499dfc
Update third_party/boringssl-with-bazel ( #32492 )
...
Upgrade boringssl to the latest "master-with-bazel"
- use the `'USE_HEADERMAP' => 'NO'` fix for ObjC
- update the key for asm optimizations on mac/apple in python's setup.py
This PR depends on monterey fixes here:
https://github.com/grpc/grpc/pull/32493 and the boringssl's build
simplification
https://boringssl-review.googlesource.com/c/boringssl/+/56465 .
---------
Co-authored-by: Hannah Shi <hannahshisfb@gmail.com>
2 years ago
Esun Kim
ea4204bb51
Update boringssl to grpc-202302 ( #32353 )
...
This is to address
[CVE-2023-0286](https://www.trellix.com/en-us/about/newsroom/stories/research/cve-2023-0286-the-openssl-who-cried-severity-high.html )
2 years ago
Jan Tattermusch
d61b564ac0
Update third_party/boringssl-with-bazel ( #28510 )
...
* Update third_party/boringssl-with-bazel
* regenerate projects
* regenerate boringssl prefix headers
* Increase boringssl podspec version
* regenerate projects (2nd time)
3 years ago
Esun Kim
5088014987
Boringssl update to 4fb1589 ( #28194 )
...
* update submodule boringssl-with-bazel with origin/main-with-bazel
* update boringssl dependency to main-with-bazel commit SHA
* regenerate files
* generate boringssl prefix headers
* Increment podspec version
3 years ago
Mark D. Roth
a54243862a
Boringssl upgrade ( #27710 )
...
* update submodule boringssl-with-bazel with origin/main-with-bazel
* update build files
* generate boringssl prefix headers
* update podspecs
3 years ago
Esun Kim
c56b0a3818
Update boringssl to the latest ( #27606 )
...
* Change boringssl branch name
* update submodule boringssl-with-bazel with origin/main-with-bazel
* update boringssl dependency to main-with-bazel commit SHA
* regenerate files
* Increment podspec version
* generate boringssl prefix headers
3 years ago
donnadionne
022cff7d7c
update submodule boringssl-with-bazel with origin/master-with-bazel ( #27208 )
...
* update submodule boringssl-with-bazel with origin/master-with-bazel
* update boringssl dependency to master-with-bazel commit SHA
* regenerate files
* Updated sha256
* generate boringssl prefix headers
* Increment podspec version
3 years ago
apolcyn
fed797b70d
Update boringssl submodule ( #26520 )
...
* update submodule boringssl-with-bazel with origin/master-with-bazel
* update boringssl dependency to master-with-bazel commit bcc01b6c66b1c6fa2816b108e50a544b757fbd7b
* regenerate projects
* Updated sha256
* Increment podspec version
* Second regeneration
3 years ago
Yash Tibrewal
fe56d1a39a
Update boringssl submodule ( #26101 )
...
* update submodule boringssl-with-bazel with origin/master-with-bazel
* Update boringssl dependency to master-with-bazel commit SHA
* Generate projects
* Updated boringssl sha256
* Generate boringssl prefix headers
* Increment podspec version
4 years ago
Karthik Ravi Shankar
26f85ca2d9
Update boringssl ( #25564 )
...
* update submodule boringssl-with-bazel with origin/master-with-bazel
* update boringssl dependency to master-with-bazel commit SHA
* regenerate files
* Updated sha256
* generate boringssl prefix headers
* Increment podspec version
* Second regeneration
* add boringssl SHA in check_submodules.sh
4 years ago
Lidi Zheng
efb01629d2
generate boringssl prefix headers
4 years ago
Lidi Zheng
027ab0a03c
generate boringssl prefix headers
4 years ago
yulin-liang
8383c5a94f
generate boringssl prefix headers
4 years ago
Donna Dionne
21367b24b5
generate boringssl prefix headers
4 years ago
Srini Polavarapu
9f68c0ab28
generate boringssl prefix headers
4 years ago
Micah Kornfield
596dcc555d
fix gen_build_yaml.py formatting
4 years ago
Micah Kornfield
8e501c86f5
Move over to using sources.json from boring.ssl.
...
- Undo a bunch of hacks in src/boringssl/gen_build_yaml.py
- Store the structued data in YAML/dependencies.py so
we don't need to recreate the filters.
- Update setup.py accordingly
4 years ago
Micah Kornfield
35c0a4cfff
Adds option of using ASM for BoringSSL in Python.
...
- Adds a new environment variable for turning on the build of ASM
for boring SSL.
- Only enables for x86_64 for now. I think this is likely the most
common target and the only machine I have readily accessible.
4 years ago
Micah Kornfield
b5efeecf31
Fallback to google3 path of sources.json if initial link doesn't work
4 years ago
Micah Kornfield
a8aeb280be
Revert "Merge pull request #23652 from grpc/revert-23568-use_sources"
...
This is a rollback of rollback to depend on sources.json for boringssl.
This reverts commit eaa670510c
, reversing
changes made to 5488e7b5cd
.
4 years ago
Karthik Ravi Shankar
52cde540a4
Revert "Uses sources.json from BoringSSL"
4 years ago
emkornfield
ddd25a7ddb
Update gen_build_yaml.py
...
remove space.
4 years ago
Micah Kornfield
1bc973bd48
Uses sources.json from BoringSSL
...
This change undoes some hackiness that relied
on specifics of the BoringSSL build system to
generate source files. With the latest github
mirror of BoringSSL exports a sources.json
that lists all source code files. This change
makes use of that file.
4 years ago
Micah Kornfield
94864fa0db
revert gen_build_yaml.py
4 years ago
Micah Kornfield
db05deb143
uses sources.json
4 years ago
Micah Kornfield
cf086ae3fa
Uses sources.json
4 years ago
Jan Tattermusch
d3144dc6b7
generate boringssl prefix headers
4 years ago
Srini Polavarapu
ce52c1dd71
update boringssl
5 years ago
Muxi Yan
65e24bcfc9
make generated header idempotent
5 years ago
Muxi Yan
389c076bdb
fix regeneration script with boringssl-with-bazel
5 years ago
Muxi Yan
215a192de3
Remove .gz.b64
5 years ago
Jan Tattermusch
9ad0a632b5
regenerate projects
5 years ago
Jan Tattermusch
5d9a67a56d
use third_party/boringssl-with-bazel/err_data.c instead of err_data.c
5 years ago
Jan Tattermusch
7ef862ddb9
do not generate crypto_test_data.cc
5 years ago