Skip to content

Avoid vulnerable pip; use uv and newer certifi - #462

Open
rclune wants to merge 1 commit into
mainfrom
fix/uv_pip_certificates
Open

rclune wants to merge 1 commit into
mainfrom
fix/uv_pip_certificates

Conversation

@rclune

@rclune rclune commented Oct 28, 2026

Copy link
Copy Markdown
Member

No pip release supporting Python 3.9 includes the fix for the October 2026 emSign CA certificate incident (the fixed pip needs Python 3.10+).

Dockerfile: install uv 0.13.6 and use it instead of pip for all package installs, add ca-certificates, and pin certifi>=2026.10.19 and numpy<2.

env/SE3nv.yml: require certifi>=2026.10.19 in the conda pip section.

README: add a note explaining how to run the pip install steps with uv 0.13.4+ inside the conda environment.

Also removes trailing whitespace on the apt-get line in the Dockerfile.

These changes are due to the security issue outlined here: https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576

No pip release supporting Python 3.9 includes the fix for the October 2026 emSign CA certificate incident (the fixed pip needs Python 3.10+).

Dockerfile: install uv 0.13.6 and use it instead of pip for all package installs, add ca-certificates, and pin certifi>=2026.10.19 and numpy<2.

env/SE3nv.yml: require certifi>=2026.10.19 in the conda pip section.

README: add a note explaining how to run the pip install steps with uv 0.13.4+ inside the conda environment.

Also removes trailing whitespace on the apt-get line in the Dockerfile.

These changes are due to the security issue outlined here: https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant