-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Mitigate the PyPI API token #7731
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I guess we should check the security history of all the following PyPI repositories: https://pypi.org/project/pymc-nightly/ Not sure what's up with the 4th one. 🤦♂ |
|
|
|
I checked my email for the |
@fonnesbeck, could you please log in to PyPI and revoke any tokens associated with your account? Everything should now be using trusted publishing, so any tokens you might still have are a security liability. |
All tokens removed. |
Thanks @fonnesbeck! |
Uh oh!
There was an error while loading. Please reload this page.
Description
(See also pymc-devs/pytensor#1306)
Description
There's currently an API token for PyPI in the secrets that we're no longer using since we migrated to trusted publishing in #7622. (Project admins can see the token here, but I don't have access.)
While we could and should delete this token from this repo's secrets, it would be much better if we could deactivate the token first. (Otherwise there's a perpetual risk that the token unexpectedly exists somewhere and could still be compromised.)
As far as I can tell, the only way to figure out the provenance of a PyPI token is for an admin to examine the project's Security history page and look at the logs from before we enabled trusted publishing to see whose account controls the token. (I don't have access.)
CC @twiecki, @fonnesbeck, @michaelosthege
The text was updated successfully, but these errors were encountered: