Repository navigation
Conversation
EDM verifies its connection to EDS against the CA bundle inside the installer; every release through 4.1.6 ships a pre-incident bundle. 4.1.7 (2026-10-23) carries certifi 2026.10.19. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
No macOS build of EDM 4.1.7 exists; the osx_x86_64 4.1 path returns 403. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
CI note + fix: |
|
Closing: codetools' |
eMudhra / emSign CA compromise — EDM client 4.1.7
EDM verifies its connection to EDS against the CA bundle shipped inside the installer, and every EDM release through 4.1.6 ships a bundle from before the incident. EDM 4.1.7 (2026-10-23) carries certifi 2026.10.19 in the client bundle and in its embedded Python 3.11.16+3 runtime. The
enthought/edm-*base images were rebuilt with 4.1.7 today (enthought/edm-containers#60).What this PR changes
.github/workflows/test-with-edm.yml:INSTALL_EDM_VERSION3.3.1 → 4.1.7 andsetup-edm-action@v1→@v4.2(the v1–v3 actions download from the pre-4.xrh6_x86_64/.../_linux_x86_64.shlayout and cannot fetch a 4.x installer). CI-only: the EDM client that downloads eggs and runtimes from EDS during the test run.Rebuilding after merge also picks up Python runtime 3.11.16+3 and the certifi 2026.10.19 / pip 26.2.2 eggs from EDS, since the
edm installcalls here float on 3.11. No build or deploy is triggered by this PR.Advisory: https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576
🤖 Generated with Claude Code