Python 3.13 / OpenSSL 3.5.5 crashes on Windows with OPENSSL_Uplink ... no OPENSSL_Applink when SSLKEYLOGFILE is set

Bug report

Bug description:

Title: Python 3.13 / OpenSSL 3.5.5 crashes on Windows with OPENSSL_Uplink ... no OPENSSL_Applink when SSLKEYLOGFILE is set

Environment:

• OS: Windows
• Python: 3.13.12, 64-bit
• OpenSSL: OpenSSL 3.5.5 27 Jan 2026
• Application: ComfyUI Desktop / ComfyUI Manager
• GPU: NVIDIA RTX 3060

Problem:
When SSLKEYLOGFILE is set, Python exits immediately during HTTPS/network activity with:

OPENSSL_Uplink(...): no OPENSSL_Applink

There is no Python traceback because the process aborts in native OpenSSL code.

Reproduction:

1. Set an environment variable:

SSLKEYLOGFILE=E:\AI\Apps\Wireshark\sslkeys.log

2. Start ComfyUI with Manager public/network mode enabled.
3. During ComfyUI-Manager startup network/cache fetches, Python exits with:

OPENSSL_Uplink(...): no OPENSSL_Applink

Observed:
The process exits with code 1. No Python exception is raised.

Expected:
Setting SSLKEYLOGFILE should enable TLS key logging or fail gracefully, not abort the Python process.

Investigation:

• import ssl works.
• import aiohttp.resolver works.
• import requests, urllib3, github, and huggingface_hub work.
• ComfyUI runs in offline mode.
• ComfyUI Manager public mode crashes during online cache/network fetching.
• ProcMon showed access to E:\AI\Apps\Wireshark\sslkeys.log immediately before the crash.
• Clearing the environment variable fixes the issue:

set SSLKEYLOGFILE=

After removing SSLKEYLOGFILE, ComfyUI Manager starts successfully in public mode.

Workaround:
Remove SSLKEYLOGFILE from User/System environment variables.

Question:
Is this a known issue with Python 3.13 / OpenSSL 3.5.x on Windows when TLS key logging is enabled?

CPython versions tested on:

3.13

Operating systems tested on:

Windows

Beginnen Sie damit, den SSLKEYLOGFILE-Fehler unter Windows mit Python 3.13 und OpenSSL 3.5.5 während der beschriebenen HTTPS-Aktivität zu reproduzieren; im Bericht wird keine CPython-Quelldatei und kein Test genannt. Als erledigt gilt die Ermittlung, ob CPython verantwortlich ist, und die Sicherstellung, dass die Schlüsselprotokollierung den Prozess nicht mehr abbricht, wobei das Public-Mode-Szenario von ComfyUI Manager als Validierung dient.