Skip to content
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.

Sign up for GitHub

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

Jump to bottom

GPG Short IDs are vulnerable to collision attacks #24

Closed
dstufft opened this issue Jul 21, 2013 · 2 comments
Closed

GPG Short IDs are vulnerable to collision attacks #24

dstufft opened this issue Jul 21, 2013 · 2 comments
Milestone
5: Shut Down Lega...

Comments

@dstufft
Copy link
Member

dstufft commented Jul 21, 2013

As @alex mentioned in #23 the GPG Short IDs used by PyPI are vulnerable to collision attacks. Once we strangle out PyPI's legacy code we should update it to use long ids or full fingerprints.
@dstufft dstufft mentioned this issue Jul 21, 2013
Merged
@dstufft dstufft mentioned this issue Mar 8, 2015
Closed
@brainwane brainwane added this to the 4) Shut down legacy site milestone Jun 30, 2016
@nlhkabu nlhkabu modified the milestones: 4: Shut down legacy site, 3: Feature parity with PyPI Jul 1, 2016
@dstufft
Copy link
Member Author

dstufft commented Jun 22, 2017

Better idea: GPG sucks and we're just not going to support it and we're going to pretend it doesn't exist. TUF is the way of the future for us.

@dstufft dstufft closed this as completed Jun 22, 2017
@alex
Copy link
Member

alex commented Jun 22, 2017

TRUE STORY

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
5: Shut Down Legacy PyPI
Development

No branches or pull requests
4 participants
@alex @dstufft @brainwane @nlhkabu