-
Notifications
You must be signed in to change notification settings - Fork 184
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
presentations: add OpenSSF Day EU slides (#271)
Also cleans up some formatting. Signed-off-by: William Woodruff <william@trailofbits.com>
- Loading branch information
Showing
3 changed files
with
25 additions
and
3 deletions.
There are no files selected for viewing
This file contains 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
21 changes: 21 additions & 0 deletions
21
presentations/Trusted Publishing: Lessons from PyPI/README.md
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Trusted Publishing: Lessons from PyPI | ||
|
||
This talk will provide a developer-minded introduction to "trusted publishing," | ||
an OpenID Connect-based authentication scheme that PyPI has successfully | ||
deployed to reduce the need for (and risk associated with) manual configured | ||
API tokens. Thousands of packages (including many of Python's most critical | ||
packages) have already enrolled in trusted publishing, improving the overall | ||
security posture (and audibility) of the Python ecosystem. | ||
|
||
We will cover trusted | ||
publishing in two parts: the first part will be a high-level overview of the | ||
trusted publishing scheme and how it uses ephemeral OpenID Connect credentials, | ||
including motivation for the scheme's security properties and how they improve | ||
upon pre-existing package index authentication schemes (e.g. user/password pairs | ||
and long-lived API tokens). The second part will dive into the nitty-gritty | ||
details of how trusted publishing was implemented on PyPI, and will serve as | ||
both a retrospective on the work and a reference for other package indices | ||
considering similar models: it will cover some of the challenges posted by OIDC | ||
(including support for multiple identity providers), threat model | ||
considerations, as well as "knock-on" benefits (such as future adjoiners with | ||
code-signing schemes like Sigstore). |
Binary file added
BIN
+2.77 MB
...entations/Trusted Publishing: Lessons from PyPI/Trusted Publishing: Lessons from PyPI.pdf
Binary file not shown.