This doesn't come up in practice as nobody would ever have such a misbehaving build in a supported released config.
Not a security issue.
./configure --with-ssl-default-suites="" && make -j24
./python -m test test_ssl
... SIGSEGV ...
The desired result is a Python exception. Clearly nobody builds intentionally with the above flag as it would've crashed when they tried to use their build. I encountered this error a different way due to a non-functional ssl library config.
Bug report
What happened?
This doesn't come up in practice as nobody would ever have such a misbehaving build in a supported released config.
Not a security issue.
I stumbled upon this while working on my draft #116399 BoringSSL linkage branch in my own non-OpenSSL Linux environment.
Steps to reproduce
The desired result is a Python exception. Clearly nobody builds intentionally with the above flag as it would've crashed when they tried to use their build. I encountered this error a different way due to a non-functional ssl library config.
CPython versions tested on:
CPython main branch
Linked PRs
_ssl._SSLContextconstructor #117309_ssl._SSLContextconstructor (GH-117309) #117317_ssl._SSLContextconstructor (GH-117309) #117318