Skip to content
Try Gitea Cloud ☁️ for 30 days → Accelerate your Development & Deploys!
Support

Verify Downloads

Every Gitea Enterprise release file is signed with GPG (.asc) and with cosign (.sigstore.json), and has a checksum (.sha256). The container images are signed with cosign and carry SBOM and provenance attestations. The files are available from https://dl.gitea.com/gitea-ee/<version>/, and the public keys are stored in https://dl.gitea.com/gitea-ee/keys/:

File Purpose
gitea-ee-release.pub.asc GPG public key of the release signatures
cosign.pub cosign public key of the release files and of the container images
FINGERPRINTS.txt and FINGERPRINTS.txt.asc Fingerprints of the keys above, signed with the GPG key
security-data.pub Public key of the security data Gitea Enterprise downloads, you do not need it to verify a release

Compare the fingerprints in FINGERPRINTS.txt with the release notes before you trust a key. Install GnuPG and cosign to run the checks below.

Here for linux-amd64, use darwin-arm64, linux-arm64 and so on for other platforms:

Terminal window
VERSION=28.4.0
BASE=https://dl.gitea.com/gitea-ee
FILE=gitea-ee-${VERSION}-linux-amd64
curl -LO "$BASE/$VERSION/$FILE"
curl -LO "$BASE/$VERSION/$FILE.sha256"
curl -LO "$BASE/$VERSION/$FILE.asc"
curl -LO "$BASE/$VERSION/$FILE.sigstore.json"
curl -LO "$BASE/keys/gitea-ee-release.pub.asc"
curl -LO "$BASE/keys/cosign.pub"
# checksum (on macOS use: shasum -a 256 -c "$FILE.sha256")
sha256sum -c "$FILE.sha256"
# GPG
gpg --import gitea-ee-release.pub.asc
gpg --fingerprint release@gitea.com # compare with FINGERPRINTS.txt
gpg --verify "$FILE.asc" "$FILE"
# cosign
cosign verify-blob --key cosign.pub --bundle "$FILE.sigstore.json" "$FILE"

gpg reports that the key is not certified with a trusted signature unless you have signed it yourself, which is expected. Check that the line Good signature from "Gitea Enterprise Release <release@gitea.com>" is printed. cosign prints Verified OK.

In PowerShell, with Gpg4win and cosign installed:

Terminal window
$Version = "28.4.0"
$Base = "https://dl.gitea.com/gitea-ee"
$File = "gitea-ee-$Version-windows-amd64.exe"
foreach ($u in "$Version/$File", "$Version/$File.sha256", "$Version/$File.asc", "$Version/$File.sigstore.json", "keys/gitea-ee-release.pub.asc", "keys/cosign.pub") {
Invoke-WebRequest "$Base/$u" -OutFile (Split-Path $u -Leaf)
}
# checksum, the two values must be equal
(Get-FileHash $File -Algorithm SHA256).Hash.ToLower()
(Get-Content "$File.sha256").Split(" ")[0]
# GPG
gpg --import gitea-ee-release.pub.asc
gpg --fingerprint release@gitea.com # compare with FINGERPRINTS.txt
gpg --verify "$File.asc" $File
# cosign
cosign verify-blob --key cosign.pub --bundle "$File.sigstore.json" $File

The images are signed with the same cosign key:

Terminal window
curl -LO https://dl.gitea.com/gitea-ee/keys/cosign.pub
cosign verify --key cosign.pub commitgo/gitea-ee:28.4.0

In Kubernetes, verify the image you set as image.repository and image.tag in the same way before you deploy it.