You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are encountering a compatibility issue when using Conscrypt with older Linux distributions, specifically CentOS 6, which uses GLIBC 2.12. We have tested multiple versions of Conscrypt (from 1.4.1 to 2.5.2) and found that none are compatible with GLIBC 2.12, as they require a minimum of GLIBC 2.14.
This issue is critical for us because upgrading GLIBC is not feasible due to potential system stability and compatibility concerns with other applications.
Here's a summary of our findings with different versions and their required GLIBC versions:
Versions 2.0.0 to 2.5.2 require GLIBC 2.14 or higher.
Version 1.4.1 seems to work with GLIBC 2.12, but we need features available in later versions.
We kindly request guidance on whether:
There are any known workarounds to make later versions of Conscrypt work with GLIBC 2.12.
It's possible to build Conscrypt from source with compatibility for GLIBC 2.12, and if so, any specific flags or options we should use.
Any help or pointers you could provide would be greatly appreciated.
Thank you for your support and looking forward to your response!
Best regards,
The text was updated successfully, but these errors were encountered:
Hello Conscrypt Team,
We are encountering a compatibility issue when using Conscrypt with older Linux distributions, specifically CentOS 6, which uses GLIBC 2.12. We have tested multiple versions of Conscrypt (from 1.4.1 to 2.5.2) and found that none are compatible with GLIBC 2.12, as they require a minimum of GLIBC 2.14.
This issue is critical for us because upgrading GLIBC is not feasible due to potential system stability and compatibility concerns with other applications.
Here's a summary of our findings with different versions and their required GLIBC versions:
We kindly request guidance on whether:
Any help or pointers you could provide would be greatly appreciated.
Thank you for your support and looking forward to your response!
Best regards,
The text was updated successfully, but these errors were encountered: