mirror of
https://github.com/go-gitea/gitea.git
synced 2026-03-14 03:46:23 -05:00
[META] Publish PGP key for signing releases #2010
Closed
opened 2025-11-02 04:21:07 -06:00 by GiteaMirror
·
8 comments
No Branch/Tag Specified
main
release/v1.25
release/v1.24
release/v1.23
release/v1.22
release/v1.21
release/v1.20
release/v1.19
release/v1.18
release/v1.17
release/v1.16
release/v1.15
release/v1.14
release/v1.13
release/v1.12
release/v1.11
release/v1.10
release/v1.9
release/v1.8
v1.25.3
v1.25.2
v1.25.1
v1.25.0
v1.24.7
v1.25.0-rc0
v1.26.0-dev
v1.24.6
v1.24.5
v1.24.4
v1.24.3
v1.24.2
v1.24.1
v1.24.0
v1.23.8
v1.24.0-rc0
v1.25.0-dev
v1.23.7
v1.23.6
v1.23.5
v1.23.4
v1.23.3
v1.23.2
v1.23.1
v1.23.0
v1.23.0-rc0
v1.24.0-dev
v1.22.6
v1.22.5
v1.22.4
v1.22.3
v1.22.2
v1.22.1
v1.22.0
v1.23.0-dev
v1.22.0-rc1
v1.21.11
v1.22.0-rc0
v1.21.10
v1.21.9
v1.21.8
v1.21.7
v1.21.6
v1.21.5
v1.21.4
v1.21.3
v1.21.2
v1.20.6
v1.21.1
v1.21.0
v1.21.0-rc2
v1.21.0-rc1
v1.20.5
v1.22.0-dev
v1.21.0-rc0
v1.20.4
v1.20.3
v1.20.2
v1.20.1
v1.20.0
v1.19.4
v1.21.0-dev
v1.20.0-rc2
v1.20.0-rc1
v1.20.0-rc0
v1.19.3
v1.19.2
v1.19.1
v1.19.0
v1.19.0-rc1
v1.20.0-dev
v1.19.0-rc0
v1.18.5
v1.18.4
v1.18.3
v1.18.2
v1.18.1
v1.18.0
v1.17.4
v1.18.0-rc1
v1.19.0-dev
v1.18.0-rc0
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.17.0-rc2
v1.16.9
v1.17.0-rc1
v1.18.0-dev
v1.16.8
v1.16.7
v1.16.6
v1.16.5
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
v1.15.11
v1.17.0-dev
v1.16.0-rc1
v1.15.10
v1.15.9
v1.15.8
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.14.7
v1.15.0
v1.15.0-rc3
v1.14.6
v1.15.0-rc2
v1.14.5
v1.16.0-dev
v1.15.0-rc1
v1.14.4
v1.14.3
v1.14.2
v1.14.1
v1.14.0
v1.13.7
v1.14.0-rc2
v1.13.6
v1.13.5
v1.14.0-rc1
v1.15.0-dev
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.6
v1.13.0-rc2
v1.14.0-dev
v1.13.0-rc1
v1.12.5
v1.12.4
v1.12.3
v1.12.2
v1.12.1
v1.11.8
v1.12.0
v1.11.7
v1.12.0-rc2
v1.11.6
v1.12.0-rc1
v1.13.0-dev
v1.11.5
v1.11.4
v1.11.3
v1.10.6
v1.12.0-dev
v1.11.2
v1.10.5
v1.11.1
v1.10.4
v1.11.0
v1.11.0-rc2
v1.10.3
v1.11.0-rc1
v1.10.2
v1.10.1
v1.10.0
v1.9.6
v1.9.5
v1.10.0-rc2
v1.11.0-dev
v1.10.0-rc1
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
v1.9.0-rc2
v1.10.0-dev
v1.9.0-rc1
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.8.0-rc3
v1.7.6
v1.8.0-rc2
v1.7.5
v1.8.0-rc1
v1.9.0-dev
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.7.0-rc3
v1.6.4
v1.7.0-rc2
v1.6.3
v1.7.0-rc1
v1.7.0-dev
v1.6.2
v1.6.1
v1.6.0
v1.6.0-rc2
v1.5.3
v1.6.0-rc1
v1.6.0-dev
v1.5.2
v1.5.1
v1.5.0
v1.5.0-rc2
v1.5.0-rc1
v1.5.0-dev
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.4.0-rc3
v1.4.0-rc2
v1.3.3
v1.4.0-rc1
v1.3.2
v1.3.1
v1.3.0
v1.3.0-rc2
v1.3.0-rc1
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.2.0-rc3
v1.2.0-rc2
v1.1.4
v1.2.0-rc1
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.99
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
Mirrored from GitHub Pull Request
No Label
type/docs
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/gitea#2010
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @paulcmal on GitHub (Jul 5, 2018).
Description
I couldn't find the PGP key
8C4033A23895237CB27D52D9D9B5613BEB813F99that signs the releases. I've tried many different keyservers. I've even tried importing the keys you use in the tests on this repo, but they're not the one :)After giteabot compromission, someone already suggested that you publish your key. They were given an answer that it would take place before 1.5.0.
I just thought opening an issue might help remembering about it :)
Thanks for maintaining Gitea <3
@techknowlogick commented on GitHub (Jul 5, 2018):
@paulcmal Thank you for opening this. I've just uploaded the public key to a well known key server: http://pool.sks-keyservers.net/pks/lookup?op=get&hash=on&fingerprint=on&search=0x2D9AE806EC1592E2 (or if you prefer the MIT key server https://pgp.mit.edu/pks/lookup?search=0x2d9ae806ec1592e2&op=index ).
@paulcmal commented on GitHub (Jul 5, 2018):
Sorry but i'm a bit confused. Is this a different key than the ones that were used for 1.4.3 and 1.5.0-rc1?
@lafriks commented on GitHub (Jul 5, 2018):
It's the same key. Seems to be working just fine for me:
@4oo4 commented on GitHub (Jul 8, 2018):
@lafriks This is only applicable to the binaries and not the actual git tags. I know you mentioned that the release tag signature depends on who the merger is, and "Github magic" (so more complex than the way the binaries are signed/verified), would it still be worth looking into being able to verify the git tags for those of us that build from source?
The binaries are obviously priority, but this would still be really nice to have for the source. I know that I'm able to do that with Bitcoin Core git tags, but it looks like they have only one person that signs the releases. Perhaps if there were a list of the user's keys that would be making releases, we could verify off of that?
By poking around the Github API, it looks like it's creating subkeys that are tied to something (either the Github account or the user's uploaded GPG key), but I can't figure out how to get a valid GPG key from it to verify what Github shows. I'm hoping that someone who is more familiar with Github (especially the API) can clarify what happens with signatures when doing a Squash and Merge and how to grab the right key.
Here's my attempts to try that:
For the most recent tag
v1.5.0-rc1, we can see that according to Github the release was verified with keyAECE216D007B1CCC, associated with @lafriks. When I try to retrieve that key (curl https://api.github.com/users/lafriks/gpg_keys), I get a base64 blob that is associated with that ID (in addition to key IDDFDE60A0093EB926which appears to be one that was actually uploaded):I'm curious how the raw key format differs from the public key blob (perhaps the binary key, base64 encoded?). Does anyone know how you can take that blob and turn it into a valid GPG key?
If so, we could use that to verify commits for each maintainer. I'm probably overthinking it but thought verification would be simpler to do 😺
Cheers
EDIT: OK, that's definitely a base64-encoded version of the signing key. When I decode that to binary, I can import that into GPG but can't seem to do anything with it (nor with
git verify-tag) The fingerprint does match though.@techknowlogick commented on GitHub (Jul 9, 2018):
@4oo4 you can also check out the URL from github here: https://github.com/lafriks.gpg that has an armored file of all lafriks public keys.
@4oo4 commented on GitHub (Jul 9, 2018):
@techknowlogick Ahh, that is so much easier, I wish Github had that better documented. Thanks!
So the reason it's not working for me I'm guessing is from the Github comment on that key:
The keys with the following IDs couldn't be exported and need to be reuploaded AECE216D007B1CCC, 002E9FFD10C56403@Mikaela commented on GitHub (Nov 15, 2019):
Request for reopening. I am unable to find the public key linked from https://docs.gitea.io/en-us/install-from-binary/ and SKS keyservers cannot be trusted anymore.
I think the best would be to have the public key somewhere in the repository itself or documentation.
@Mikaela commented on GitHub (Nov 15, 2019):
I was able to find this: