python / python/cpython

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

未关闭
#152,784 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

extension-modules OS-windows topic-SSL type-bug
主要语言
Python
星标
77.2k
派生
35.9k
PR 合并指标
PR 指标待抓取

描述

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

  1. Start ComfyUI with Manager public/network mode enabled.
  2. 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

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

首先,在所述的 HTTPS 活动期间,使用 Python 3.13 和 OpenSSL 3.5.5 在 Windows 上复现 SSLKEYLOGFILE 失败;报告没有指出任何 CPython 源文件或测试。完成的标准是确定 CPython 是否负有责任,并确保密钥记录不再中止进程,同时以 ComfyUI Manager 的公共模式场景作为验证。

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
operating-systems, security
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
冷清
描述清晰度
需要澄清
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。