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
A couple of users have reported issues with the SSL certificate of sweet.silkypants.dev. The app crashes with the following exception:
HandshakeException: HandshakeException: Handshake error in client (OS Error:
CERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate(../../../flutter/third_party/boringssl/src/ssl/handshake.cc:393))
After creating a debug build which dumps the certificate by overriding HTTPClient.badCertificateCallback, I have found out that the following certificate is failing:
It seems that there are multiple possible certification paths with two different versions of the Amazon Root CA 1. The one that is failing is this one: crt.sh/?id=11265962. Even though this chain is also valid/trusted, dart seems to fail resolving it properly.
I will upload a hotfix which does use the badCertificateCallback to manually trust the second certificate for this host. But this is not a very nice fix and I would appreciate further help.
The text was updated successfully, but these errors were encountered:
A couple of users have reported issues with the SSL certificate of
sweet.silkypants.dev
. The app crashes with the following exception:After creating a debug build which dumps the certificate by overriding
HTTPClient.badCertificateCallback
, I have found out that the following certificate is failing:It seems that there are multiple possible certification paths with two different versions of the Amazon Root CA 1. The one that is failing is this one: crt.sh/?id=11265962. Even though this chain is also valid/trusted, dart seems to fail resolving it properly.
The ssllabs report:
I will upload a hotfix which does use the
badCertificateCallback
to manually trust the second certificate for this host. But this is not a very nice fix and I would appreciate further help.The text was updated successfully, but these errors were encountered: