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

Aberta
#1,963 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 3 dias

@AustinBenoit já está trabalhando nisso.

Desde 13/11/2026.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
42/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
cmake, cpp, firebase
Domínio
networking

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C++
Estrelas
326
Forks
137
Merge médio
3d 8h
PRs com merge (30d)
17

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de firebase/firebase-cpp-sdk

Todas as issues de firebase/firebase-cpp-sdk

Issues semelhantes

Mais issues de C++

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.