gRPC-python wraps gRPC-Core as they are in the same repo. So if you go to the specific git tag, e.g. https://github.com/grpc/grpc/tree/v1.58.0/third_party, you can find the commit of the BorgingSSL dependency (boringssl-with-bazel ...). In this case of 1.58.0, it's https://github.com/google/boringssl/tree/2ff4b968a7e0cfee66d9f151cb95635b43dc1d5b.
On Thursday, September 14, 2023 at 10:36:15 AM UTC-7 Reena THOMAS wrote: > And what is the BoringSSL version used there? How do we decipher it > > On Wednesday, September 13, 2023 at 11:21:59 PM UTC+5:30 AJ Heller wrote: > >> I'm not entirely sure how to help you with such an old version. I'd >> recommend trying with a more recent gRPC version, we are currently up to >> version 1.58. https://pypi.org/project/grpcio/ >> >> On Monday, September 11, 2023 at 3:40:12 AM UTC-7 Reena THOMAS wrote: >> >>> I am downloading tar file from >>> https://files.pythonhosted.org/packages/fb/d5/30bc142a40bb891c28739ec48c99730d20e5fb9cf9637036b4b52f70505b/grpcio-1.21.1.tar.gz >>> >>> , and ran "python setup.py install" >>> >>> I am unable to find a clear solution to know boringSSL version that is >>> mapped to grpcio 1.21.1 >>> >>> Is there a way to find from source code or from above tar file? >>> Any help will be appreciated >>> >>> Project: https://pypi.org/project/grpcio/1.21.1/#files >>> >> -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/44b8acae-0ba8-42d9-b007-b41be19695f3n%40googlegroups.com.
