Repository navigation
pip 20.3.4.post4 (Py2.7): vendored certifi 2026.10.23.post1 - #10
Merged
Merged
Conversation
Follow-up to GHSA-6q48-6c7w-9gw2 (the eMudhra/emSign CA key compromise). Upgrade the vendored certifi from 2026.10.19.post1 to 2026.10.23.post1 (ActiveState/certifi 2026.10.23.post1, whose cacert.pem is identical to upstream certifi 2026.10.23). It removes two more emSign roots, emSign Root CA - C1 and emSign ECC Root CA - C3, after emSign ECC Root CA - G3 was removed in the previous release. emSign Root CA - G1 is now the only emSign root in the bundle. Only cacert.pem and the certifi version change in the vendored package; pip's certifi patches are untouched. The pip version is bumped to 20.3.4.post4 and NEWS.rst gains the release entry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ezequielp-activestate
approved these changes
Oct 28, 2026
ezequielp-activestate
left a comment
There was a problem hiding this comment.
No blockers. The vendored cacert.pem is byte-identical to the one in certifi 2026.10.23 on PyPI (sha256 2ef52ad5…). Against the base branch it removes exactly two roots, emSign Root CA - C1 and emSign ECC Root CA - C3, and adds none, leaving emSign Root CA - G1 as the only emSign root, as the changelog says. The pip version, the vendored certifi __version__ (2026.10.23.post1) and vendor.txt agree. That ActiveState certifi release exists with its wheel and sdist attached. On Python 2.7.18, this tree's pip reports 20.3.4.post4, certifi where() points at the vendored bundle, and pip download six==1.16.0 from PyPI succeeds over TLS through it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Security release pip 20.3.4.post4 for the Python 2.7 line. Follow-up to GHSA-6q48-6c7w-9gw2, the eMudhra/emSign CA key compromise.
Change
cacert.pemis byte-identical to upstream certifi 2026.10.23's.cacert.pemand the certifi version (in__init__.pyandvendor.txt). pip's certifi patches are unchanged. The pip version is bumped to 20.3.4.post4, and NEWS.rst gets the release entry.Validation (in
python:2.7-slim)pip --versionreports 20.3.4.post4.certifi.contents()works.pip download six==1.16.0from PyPI works.pip/__init__.py,pip/_vendor/certifi/__init__.py,pip/_vendor/certifi/cacert.pemandpip/_vendor/vendor.txt, plusRECORDand theVersion:line inMETADATA.NEWS.rstandPKG-INFO.After merge: tag
20.3.4.post4and publish a GitHub release with the wheel and sdist.