Request for PGDG Repository Signing-Key Verification — PostgreSQL 16.10

From: eric asiedu <iameric(dot)asiedu(at)gmail(dot)com>
To: pgsql-pkg-debian(at)postgresql(dot)org
Subject: Request for PGDG Repository Signing-Key Verification — PostgreSQL 16.10
Date: 2026-10-22 01:57:17
Message-ID: CAD9P572cpHnCWjdWZ6RpcQSzxLLxaZJXYTYCNZtcrLkcC3cdCA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-pkg-debian

Hello PostgreSQL APT Repository Maintainers,

I am contacting you on behalf of Aserion, an enterprise cryptographic
security and post-quantum migration assurance platform currently
undergoing a security qualification review.

As part of our software supply-chain verification, we are seeking
authoritative confirmation of the PostgreSQL Global Development Group
(PGDG) repository signing key used to authenticate PostgreSQL 16.10
source-package metadata.

Our verification identified the following:

*PGDG repository signing-key fingerprint:*
B97B0AFCAA1A47F044F244A07FCC7D46ACCC4CF8

*PostgreSQL 16.10 source archive SHA-256:*
de8485f4ce9c32e3ddfeef0b7c261eed1cecb54c9bcd170e437ff454cb292b42

*Archive size:* 24,977,722 bytes

We successfully verified the signature chain from the PGDG archived Debian
repository's InRelease metadata through its Sources.bz2 index to the exact
archive digest.

We also verified a historical third-party OpenPGP certification of the PGDG
key by Christoph Berg's key.

To complete our independent trust assessment, could you please confirm:

1.

Whether the PGDG fingerprint above is the authentic, authorized
repository signing key for the relevant repository metadata.
2.

Whether the key was authorized for signing the PostgreSQL 16.10
source-package metadata and whether there are any relevant known
compromise, revocation or replacement notices.
3.

Whether there is an authoritative historical key record, signed
statement, or independently verifiable channel that can corroborate the
key's identity.
4.

Whether the archived signed metadata is an appropriate reference for
establishing the authenticity of this exact source archive, subject to its
date and freshness limitations.

A response identifying an authoritative verification method or existing
signed evidence would be greatly appreciated. We are not requesting changes
to PostgreSQL or a new release signature.

Thank you for your assistance.

Kind regards,

Aserion Security Qualification Team

Responses

Browse pgsql-pkg-debian by date

  From Date Subject
Next Message apt.postgresql.org Repository Update 2026-10-26 11:30:55 pg-hint-plan-14 updated to version 1.4.5-1.pgdg+1
Previous Message apt.postgresql.org Repository Update 2026-10-19 15:01:43 pgbouncer updated to version 1.26.1-1.pgdg+1