Skip to content

Verify ownership of GPG key #25

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

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

Verify ownership of GPG key #25

dstufft opened this issue Jul 21, 2013 · 2 comments
Labels
feature request requires triaging maintainers need to do initial inspection of issue

Comments

@dstufft
Copy link
Member

dstufft commented Jul 21, 2013

Currently there's no verification that a person owns the GPG key they claim they do. We should verify this before allowing this key.

@brainwane
Copy link
Contributor

This would be a new feature that legacy PyPI does not support and I'm in favor of it in Warehouse. :)

@nlhkabu nlhkabu added the requires triaging maintainers need to do initial inspection of issue label Jul 2, 2016
@ewdurbin
Copy link
Member

@dstufft this is a little bit of an old issue :)

Since it's filing many issues have come and gone regarding GPG, and I am going to close this.

PEP 503 specifies PyPI's handling of signatures supplied when packages are uploaded:

PEP 101 gives overall guidance of signing commits and releases, but does not specify PyPI's behavior:

PEPs 241 and 314 both specify the same non-binding requirement that a repository might provide authors the ability to store their GPG Key... which is wholly distinct from a Key ID... but I think I know what they meant.

Given the context and reasoning given in other venues, and the ultimate fact that just asking PyPI for a users GPG Key ID rather than the Keyserver infrastructure that exists solely for this purpose, I'm closing this and removing GPG Key ID handling from pypa/pypi-legacy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request requires triaging maintainers need to do initial inspection of issue
Projects
None yet
Development

No branches or pull requests

4 participants