]> git.ipfire.org Git - thirdparty/curl.git/commitdiff
test313: disable CRL test for Schannel due to lack of support and flakiness
authorViktor Szakats <commit@vsz.me>
Fri, 28 Mar 2025 18:10:28 +0000 (19:10 +0100)
committerViktor Szakats <commit@vsz.me>
Sat, 29 Mar 2025 11:35:34 +0000 (12:35 +0100)
The source code and documentation says that CRL is not supported by
curl's Schannel TLS backend.

It's also frequently flaky in CI with both MinGW and MSVC jobs, e.g.:
https://github.com/curl/curl/actions/runs/14134841988/job/39603994164 (Schannel)
https://github.com/curl/curl/actions/runs/14134841988/job/39606336445 (Schannel)
https://github.com/curl/curl/actions/runs/13981383629/job/39147183706 (LibreSSL)

```
curl returned 35, when expecting 60
```

This test was passing with Schannel because it misses the `--insecure`
option and thus always returns 60, regardless of passing `--crlfile` or
not:
```
curl: (60) schannel: CertGetCertificateChain trust error CERT_TRUST_REVOCATION_STATUS_UNKNOWN
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the webpage mentioned above.
```

Closes #16862

tests/data/DISABLED

index 5c892555090ff75714820917a5f9cccb598af149..a3cd95e2104ae9ebe20d7fcdee1bed713dd39868 100644 (file)
 %if bearssl
 313
 %endif
+# Schannel does not support CRL file
+%if Schannel
+313
+%endif
 # Secure Transport does not support CRL file
 %if sectransp
 313