| From: | kaufman green <green(dot)kaufman(at)outlook(dot)com> |
|---|---|
| To: | "pgsql-pkg-yum(at)lists(dot)postgresql(dot)org" <pgsql-pkg-yum(at)lists(dot)postgresql(dot)org> |
| Subject: | Request for official verification of PGDG RHEL RPM signing key fingerprint |
| Date: | 2026-10-14 03:58:18 |
| Message-ID: | SI6PR06MB76591C558C412E01E83AE9A5F29D2@SI6PR06MB7659.apcprd06.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-yum |
Hello PGDG RPM Repository Maintainers,
We are preparing to install the PostgreSQL 17 client tools on an Alibaba Cloud Linux 3 (x86_64) server for a PostgreSQL 17 database backup.
Before installation, we would like to independently verify the authenticity of the PGDG RHEL RPM signing key.
The public key we obtained has the following details:
*
Key file: PGDG-RPM-GPG-KEY-RHEL
*
Primary fingerprint: D4BF08AE67A0B4C7A1DBCCD240BCA2B408B40D20
*
Key ID: 40BCA2B408B40D20
*
SHA-256 of key file: A70C9527426017D00FA4E6F9D2941D515357A27A7BE82E155248ECE53BBE5453
We have successfully verified the RPM signatures of postgresql17-17.11 and postgresql17-libs-17.11 using this key in an isolated RPM database.
Could you please confirm whether this is the authentic, currently authorized PGDG RPM signing key for RHEL 8 x86_64 packages?
If possible, please provide an authoritative published fingerprint or another independently verifiable reference.
Thank you for your assistance.
Best regards
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2026-10-15 13:47:08 | RHEL 10.0 and 9.6 repositories are being retired |
| Previous Message | Devrim Gündüz | 2026-10-12 20:29:00 | Re: PGDG RPM GPG key fingerprint verification (RHEL 8 / PostgreSQL 16) |