python: signature verification can never succeed for Python 3.14+

未关闭
  • 哪里不对？
#1,764 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@V-Subhankar-infy 已经在做这个了。

开始于 2026年11月5日。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
shell
领域
security, tooling

调研方向

Start in src/python/install.sh around lines 532-591, where the cosign and signature downloads run. Reproduce the curl exit code 2 from -f combined with --fail-with-body, then check the .sigstore URL that python.org serves for 3.14+. Done means the downloads succeed, cosign verify-blob checks the bundle against the signer identity python.org lists, and a failed check stops the build or logs a real error.

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

描述

Summary

In the python feature (1.8.0, and src/python/install.sh on main), the cosign check for Python 3.14+ always fails, so these versions are always built from source without signature verification. The build continues and logs that this is expected for newly released versions, but it happens for every version.

Causes

  1. Invalid curl flags. The cosign and signature downloads (lines 532, 544, 585, 591) pass both -f and --fail-with-body, which curl rejects with exit code 2. Most of these calls send stderr to /dev/null, and none of them surfaces the real error, so it looks like a failed download.

    curl -L -f --fail-with-body https://www.python.org/ftp/python/3.14.10/Python-3.14.10.tgz.crt -o /dev/null
# curl: option --fail-with-body: is badly used here
# exit code 2

    Reproduced with curl 8.14.1 (in a dev container built from mcr.microsoft.com/devcontainers/base:debian) and curl 8.7.1 (macOS). With --fail-with-body alone, the same request exits 0.

  2. Wrong certificate URL. Lines 580-581 look for .sig and .pem. For 3.14.10, python.org returns 200 for .sig, .crt and .sigstore, and 404 for .pem. Fixing the curl flags alone would still fail at this step.

  3. Any signer is accepted. The cosign verify-blob call uses --certificate-identity-regexp=".*" and --certificate-oidc-issuer-regexp=".*". Even a passing check wouldn't show that the Python release manager signed the file.

  4. The build continues after a failed check. If verification fails, the script logs a warning and builds the tarball anyway, and there is no checksum check. The warning says this is "expected for newly released versions where cosign signatures are not yet available", which hides the failure.

Impact

Every Python 3.14+ build from source through this feature skips signature verification. The tarball is still downloaded over HTTPS, so this doesn't create an attack by itself, but the protection that replaced PGP for 3.14+ isn't working.

Suggested fix

  1. Remove -f from the affected curl calls.

  2. Verify with the .sigstore bundle and the signer identity that python.org lists for each release series. This command returned Verified OK for 3.14.10 with cosign 3.1.4, and failed when given a different identity:

    cosign verify-blob \
  --bundle Python-3.14.10.tgz.sigstore \
  --certificate-identity [email protected] \
  --certificate-oidc-issuer https://github.com/login/oauth \
  Python-3.14.10.tgz

  3. Consider failing the build when verification fails, or at least changing the warning so it doesn't describe a failure as expected.

主要语言
Shell
星标
1.6k
派生
627
平均合并
1 天 19 小时
30 天内合并 PR
5

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

devcontainers/features 的其他 Issue

查看 devcontainers/features 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

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