Sorry for missing version;

gRPC started to support OpenSSL 3 since 1.58 (link)

On Thu, Aug 22, 2024 at 1:17 PM Esun Kim <vebl...@google.com> wrote:

> gRPC started to support OpenSSL since 1.58 (link
> <https://github.com/grpc/grpc/releases/tag/v1.58.0>)
>
> On Thu, Aug 22, 2024 at 11:31 AM 'Daksha Tulshikar' via grpc.io <
> grpc-io@googlegroups.com> wrote:
>
>> are there any plans to support openssl 3.0?
>>
>> On Thursday, January 26, 2023 at 12:05:28 AM UTC+5:30 veb...@google.com
>> wrote:
>>
>>> I don't think gRPC supports OpenSSL 3.0 yet as we have
>>> https://github.com/grpc/grpc/pull/31256 open.
>>> But it's puzzling to me that you saw many undefined errors. I expected
>>> that it should be compile errors due to API breaking changes or runtime
>>> errors due to potential API behavior changes.
>>>
>>> On Thursday, January 12, 2023 at 12:29:29 AM UTC-8 小煤球 wrote:
>>>
>>>> When I tried to compile grpc, I changed the OpenSSL version to 3.0, but
>>>> many undefined errors occurred during the compilation.
>>>>
>>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "grpc.io" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/grpc-io/V3Bp4QNGpMQ/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/5267b229-7ff3-4614-9cae-0b82785cb22an%40googlegroups.com
>> <https://groups.google.com/d/msgid/grpc-io/5267b229-7ff3-4614-9cae-0b82785cb22an%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
> Regards,
> Esun.
>
>

-- 
Regards,
Esun.

-- 
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/CAFp8MWyZZsK6RXUbCSdOvMY2NepRsyqAsjV2SGsDaggX2NCtVw%40mail.gmail.com.

Reply via email to