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

move to new signing keys #2968

Closed
totaam opened this issue Dec 7, 2020 · 3 comments
Closed

move to new signing keys #2968

totaam opened this issue Dec 7, 2020 · 3 comments
Milestone

Comments

@totaam
Copy link
Collaborator

totaam commented Dec 7, 2020

Instead of signing the packages with my personal key, create a new one (stronger too) for the project and ensure that other trusted developers can take it over if needed. (and store it on a hardware token to keep it safe)

The difficult part is going to be the transition, as packages can only be signed by a single key.
New packages could just add the new signing key to the system (ie: rpm --import) and eventually (6 months?) we can switch over to the new key without causing too many problems?

@totaam
Copy link
Collaborator Author

totaam commented Dec 7, 2020

@totaam totaam added this to the 4.1 milestone Jan 23, 2021
@totaam totaam mentioned this issue Jan 24, 2021
@totaam
Copy link
Collaborator Author

totaam commented Jan 24, 2021

The new key is here:
http://xpra.org/xpra.asc
And is already used with github through a yubikey.

Will follow up with package signing in #1830

@totaam
Copy link
Collaborator Author

totaam commented Jul 4, 2023

Newer ticket for GPG keys: #3863

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

No branches or pull requests

1 participant