Windows: sign-in fails behind TLS inspection because the Schannel revocation check is strict (CRYPT_E_NO_REVOCATION_CHECK)

Offen
#1,963 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 3 Tagen

@AustinBenoit arbeitet bereits daran.

Seit 13.11.2026.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
42/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
cmake, cpp, firebase
Bereich
networking

Rechercherichtung

Start in app/rest/transport_curl.cc, in BackgroundTransportCurl::PerformBackground, where CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST are set, and confirm no CURLOPT_SSL_OPTIONS call exists. Check the curl version pinned in CMakeLists.txt and cmake/external/curl.cmake to confirm CURLSSLOPT_REVOKE_BEST_EFFORT is available. Done means a Windows-only option is set without changing peer or host verification, and a test or manual check against a revocation-unavailable chain passes.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

needs-triage

On Windows, sign-in through the C++ SDK fails on company networks that inspect TLS. We hit this through FlutterFire (firebase_core 4.15.2, which downloads firebase_cpp_sdk_windows_13.13.1.zip). signInWithCredential and signInWithEmailAndPassword both return [firebase_auth/unknown-error] An internal error has occurred, while browsers and the rest of our app reach Google from the same machine without trouble.

One affected user traced it on their machine. Schannel returns CRYPT_E_NO_REVOCATION_CHECK (0x80092012). Their company's inspection CA is trusted in the Windows root store, but the leaf certificates it issues carry no CRL distribution point and no OCSP URL, so the revocation check can't run. This is the fifth separate report we've had since June, and flutterfire#12725 looks like the same failure.

The REST transport builds libcurl with Schannel on Windows (CMAKE_USE_SCHANNEL ON in CMakeLists.txt at v13.13.1, CURL_USE_SCHANNEL ON on main). BackgroundTransportCurl::PerformBackground in app/rest/transport_curl.cc sets CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST and never sets CURLOPT_SSL_OPTIONS. With curl's Schannel backend that makes a revocation check that can't be completed fatal. Browsers treat that case as a soft failure, which is why they keep working on these networks. As far as I can tell main is the same: I found no CURLOPT_SSL_OPTIONS there either.

Would you take a change that sets CURLSSLOPT_REVOKE_BEST_EFFORT on Windows, next to the two existing verify lines?

#if defined(_WIN32)
  CheckOk(curl_easy_setopt(curl_, CURLOPT_SSL_OPTIONS,
                           static_cast<long>(CURLSSLOPT_REVOKE_BEST_EFFORT)),
          "ssl options");
#endif

Peer and host verification stay on, and a certificate that is checked and found revoked still fails. The only case that changes is the one where revocation status can't be obtained. The option needs curl 7.70 or later. v13.13.1 bundles 7.73.0 and main bundles 8.23.0 (cmake/external/curl.cmake).

I can open the PR if you're fine with this approach. The user who traced the error has offered to test a build.

Vorherrschende Sprache
C++
Sterne
326
Forks
137
Ø Merge
3 T. 8 Std.
Gemergte PRs (30 T.)
17

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus firebase/firebase-cpp-sdk

Alle Issues in firebase/firebase-cpp-sdk

Ähnliche Issues

Weitere Issues zu C++

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.