github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Can't verify the signature of gitea binary as per instructions #6936

New Issue
Closed
opened 2025-11-02 07:11:40 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 07:11:40 -06:00
Owner
Copy Link

Originally created by @oreza on GitHub (Feb 27, 2021).

  • Gitea version (or commit ref): 1.13.2-linux-amd64
  • Git version: 2.25.1
  • Operating system: Ubuntu 20.04.2 LTS
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:

Description

Can't verify the signature of gitea binary as per instructions

Steps:
1 - gpg --keyserver keys.openpgp.org --recv 7C9E68152594688862D62AF62D9AE806EC1592E2
2 - Download gitea-1.13.2-linux-amd64.asc
3 - Download gitea-1.13.2-linux-amd64
4 - gpg --verify gitea-1.13.2-linux-amd64.asc gitea-1.13.2-linux-amd64

gpg: Signature made Tue 02 Feb 2021 12:37:53 AM UTC
gpg:                using RSA key CC64B1DB67ABBEECAB24B6455FC346329753F4B0
gpg: Good signature from "Teabot <teabot@gitea.io>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 7C9E 6815 2594 6888 62D6  2AF6 2D9A E806 EC15 92E2
     Subkey fingerprint: CC64 B1DB 67AB BEEC AB24  B645 5FC3 4632 9753 F4B0
Originally created by @oreza on GitHub (Feb 27, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.13.2-linux-amd64 - Git version: 2.25.1 - Operating system: Ubuntu 20.04.2 LTS <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [X] Yes (provide example URL) - [ ] No - Log gist: <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description <!-- If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services. --> Can't verify the signature of gitea binary as per instructions Steps: 1 - gpg --keyserver keys.openpgp.org --recv 7C9E68152594688862D62AF62D9AE806EC1592E2 2 - Download gitea-1.13.2-linux-amd64.asc 3 - Download gitea-1.13.2-linux-amd64 4 - gpg --verify gitea-1.13.2-linux-amd64.asc gitea-1.13.2-linux-amd64 ``` gpg: Signature made Tue 02 Feb 2021 12:37:53 AM UTC gpg: using RSA key CC64B1DB67ABBEECAB24B6455FC346329753F4B0 gpg: Good signature from "Teabot <teabot@gitea.io>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 7C9E 6815 2594 6888 62D6 2AF6 2D9A E806 EC15 92E2 Subkey fingerprint: CC64 B1DB 67AB BEEC AB24 B645 5FC3 4632 9753 F4B0 ```
GiteaMirror added the type/docs label 2025-11-02 07:11:40 -06:00
GiteaMirror commented 2025-11-02 07:11:41 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 27, 2021):

This is not true. Gpg is verifying the signature as good.

What it's reporting is that you don't trust the key that verifies that signature.

That's your gpg trust level for teabot@gitea.io not ours.

We've listed the gpg key in as many places as we can - keys.openpgp.org won't let you search for a key by email address unless a nonce sent to that email can be verified with the private key - we're on the sks pool and I think you can get the key on gitea.com too.

Your level of whether you want to trust this key as the gitea project is up to you - I think we've done all we can to reasonably assure that this is the gitea project's key and so you should raise your personal trust level for the key - but gpg is telling you that it verifies signature.

@zeripath commented on GitHub (Feb 27, 2021): This is not true. Gpg is verifying the signature as good. What it's reporting is that you don't trust the key that verifies that signature. That's your gpg trust level for teabot@gitea.io not ours. We've listed the gpg key in as many places as we can - keys.openpgp.org won't let you search for a key by email address unless a nonce sent to that email can be verified with the private key - we're on the sks pool and I think you can get the key on gitea.com too. Your level of whether you want to trust this key as the gitea project is up to you - I think we've done all we can to reasonably assure that this is the gitea project's key and so you should raise your personal trust level for the key - but gpg is telling you that it verifies signature.
GiteaMirror commented 2025-11-02 07:11:41 -06:00
Author
Owner
Copy Link

@oreza commented on GitHub (Feb 28, 2021):

Thank you

@oreza commented on GitHub (Feb 28, 2021): Thank you
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Mirrored from GitHub 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
No Label type/docs
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6936
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?