logoalt Hacker News

skeledrew • yesterday at 12:34 PM • 3 replies • view on HN

Because pip uses it's own certificate bundle, so even if you fix the system itself pip still needs its own upgrade to handle the eMudhra episode.


Replies

tetha • yesterday at 1:56 PM

And strictly speaking you cannot trust the pip upgrade of pip with the vulnerable cert in the trust store due to certifi, which you also cannot upgrade safely with pip for the same reason. All of these are at one out of two compromises from being MITM'd during the upgrade.

So strictly we have to burn everything python to the ground and reinstall entirely.

➕ show 2 replies
zahlman • today at 5:25 AM

~~Recent versions of pip use `truststore` by default to access the system's certificates, only relying on the vendored `certifi` as a fallback or if explicitly directed.~~

The above is incorrect per the Python forum discussion (https://discuss.python.org/t/information-for-python-users-re...). Pip will trust certificates from both sources.

Users of uv who have already updated their system certificates can use:

  UV_SYSTEM_CERTS=true uv self update
steve1977 • yesterday at 3:43 PM

Python certificate handling is a hot mess, even by Python standards.