GeistHaus
log in · sign up

Introduction

docs.pypi.org
7 pages link to this URL
Why Use Trusted Publishing for PyPI?

Trusted publishing replaces long-lived PyPI API tokens with short-lived OIDC credentials, eliminating the most common way attackers gain unauthorized upload access to PyPI.

0 inbound links article en handbook
Attestations: A new generation of signatures on PyPI

For the past year, we’ve worked with the Python Package Index (PyPI) on a new security feature for the Python ecosystem: index-hosted digital attestations, as specified in PEP 740. These attestations improve on traditional PGP signatures (which have been disabled on PyPI) by providing key usability, index verifiability, cryptographic strength, and provenance properties that bring […]

1 inbound link article en open-sourcesupply-chainecosystem-securityengineering-practice open-sourcesupply-chainecosystem-securityengineering-practice
Attestations: A new generation of signatures on PyPI

For the past year, we’ve worked with the Python Package Index (PyPI) on a new security feature for the Python ecosystem: index-hosted digital attestations, as specified in PEP 740. These attestations improve on traditional PGP signatures (which have been disabled on PyPI) by providing key usability, index verifiability, cryptographic strength, and provenance properties that bring […]

3 inbound links article en open-sourcesupply-chainecosystem-securityengineering-practice open-sourcesupply-chainecosystem-securityengineering-practice
Why pylock.toml includes digital attestations

A Python project got hacked where malicious releases were directly uploaded to PyPI. I said on Mastodon that had the project used trusted publishing with digital attestations, then people using a pylock.toml file would have noticed something odd was going on thanks to the lock file including attestation data.

2 inbound links article en Pythonpackaging