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.

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

Listing the keys in the used in the repository. #9

Open
da2ce7 opened this issue May 3, 2022 · 2 comments
Open

Listing the keys in the used in the repository. #9

da2ce7 opened this issue May 3, 2022 · 2 comments

Comments

@da2ce7
Copy link
Contributor

da2ce7 commented May 3, 2022

Bitcoin has a file within their repository that lists the GPG key-fingerprints that are used by the developers and builders.

https://github.com/bitcoin/bitcoin/tree/master/contrib/builder-keys

This is a good way to authenticate a new developer for the project.

I think that the GPG-Bootcamp could explain how to upload a key to the keysever, and request for listing in the keys.txt file.

@da2ce7 da2ce7 changed the title Uploading a key to the Keyserver, so others can download the keys. Listing the keys in the used in the repository. May 3, 2022
@cgbosse
Copy link
Member

cgbosse commented May 11, 2022

I looked at the link and repo.
This can be implemented. However, given that we have 18 repositories to date I think that we should use a central file for this and have it in the organization repository.

One question though:
The yellow part in the screenshot we do not need, ¿correct? Each ones key is imported into GitHub from his profile.

image

@josecelano
Copy link
Member

This is related to a new article proposal I have added.

With the keys.txt file you can get the list of public keys. And you can use a Git Tag to obtain the public key instead of using an external GPG server like http.

I do not know the pros and cons of using your own key server vs a well-known one.

cc @da2ce7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants