-
Notifications
You must be signed in to change notification settings - Fork 196
GPG Key Setup
Ed Espino edited this page Jun 6, 2025
·
3 revisions
To verify the integrity and authenticity of the release artifacts, use the Apache PGP process:
- Import the release manager’s public key (if not already trusted):
curl https://dist.apache.org/repos/dist/dev/incubator/cloudberry/KEYS | gpg --import- Verify the signature of the source release artifact:
gpg --verify apache-cloudberry-2.0.0-incubating-rc1-src.tar.gz.asc apache-cloudberry-2.0.0-incubating-rc1-src.tar.gzExpected output:
gpg: Good signature from "Ed Espino <[email protected]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
sha512sum -c apache-cloudberry-2.0.0-incubating-rc1-src.tar.gz.sha512Expected output:
apache-cloudberry-2.0.0-incubating-rc1-src.tar.gz: OK
For more information, see the [Apache Release Signing Guide](https://www.apache.org/dev/release-signing.html).