Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

SECURITY ADVISORY: Stop using bundled eMudhra root certificate

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by tracing the SDK's stripe.ca_bundle_path configuration and how the bundled CA file is loaded and tested. Identify which supported major versions still include the affected eMudhra root and ensure they avoid it or use the operating system certificate bundle. Done means affected versions no longer use the compromised root, with tests covering the certificate selection behavior.

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

描述

Stripe is aware of the eMudhra intermediate certificate compromise. Since v4.0, the Stripe Python SDK has shipped with a root certificate bundle that includes an affected root certificate. Stripe’s internal review found no certificates for Stripe domains that chain through the affected intermediates. Even so, we have updated the root certificate bundle in the repo and have published patches with the updated bundle for every major version back to v4. See https://github.com/stripe/stripe-python/issues/1954#issuecomment-6431170002 below for links to the patch releases.

If you cannot upgrade your SDK, you can still limit exposure to this issue by updating your operating system's trusted root certificates and configuring the Stripe SDK to use the default certificate file:

import stripe

# After importing, manually configuring `stripe` to use the default certificate bundle
stripe.ca_bundle_path = ssl.get_default_verify_paths().openssl_cafile
主要语言
Python
星标
2.1k
派生
543
平均合并
3 天 21 小时
30 天内合并 PR
15

环境准备

从这里开始

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

stripe/stripe-python 的其他 Issue

查看 stripe/stripe-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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