Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vi9Ks-00GTcB-1c for pgsql-general@arkaria.postgresql.org; Tue, 20 Jan 2026 10:51:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vi9Kr-000YD3-1b for pgsql-general@arkaria.postgresql.org; Tue, 20 Jan 2026 10:51:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vi9Kr-000YCu-0F for pgsql-general@lists.postgresql.org; Tue, 20 Jan 2026 10:51:45 +0000 Received: from mout-u-204.mailbox.org ([80.241.59.204]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vi9Kn-001PIb-36 for pgsql-general@postgresql.org; Tue, 20 Jan 2026 10:51:44 +0000 Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-204.mailbox.org (Postfix) with ESMTPS id 4dwPJn48M2z9sq3; Tue, 20 Jan 2026 11:51:37 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1768906297; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pZz1k9CmBq1VNgU8VfJKZpXhWfdPGoLKyaNVh+jn5qA=; b=gBmM611iJ0Mc/O7rrDh6Ih1TKaG627SPeOirs8vjw1Nell8AxIYoYRn4ykTdBYsifJchH7 axyp+QjvZNhTHdNyTwvIQROPavOJg+awmORfY47Gib15EleK79RFrNwMbF0s6pw+yiPt3A J6wkV3XOYrztRS1DQdU/kwlSToJH86Qurf6BaeVksVXtpP+5x3OHAypuC/vAzW3cBj2BmN v29ioPjFa0+LZrEIh0wht6jxTvhe+lekMCj8+0jcrWmpdMEiU2QZ7JPFnlhFI4xgGgUekR ypu0pXdYUfqwzwPYL2GKi94wBpOFMfOaxs1ICYXiYu5OgyPNCUHtj2h5FvJCzw== Authentication-Results: outgoing_mbo_mout; dkim=none; spf=pass (outgoing_mbo_mout: domain of ewie@ewie.name designates 2001:67c:2050:b231:465::202 as permitted sender) smtp.mailfrom=ewie@ewie.name Date: Tue, 20 Jan 2026 11:51:35 +0100 From: Erik Wienhold To: ManiR Cc: pgsql-general@postgresql.org Subject: Re: Request for cryptographic mechanisms used in PostgreSQL Message-ID: <9e3ecb34-7132-4ce7-9c62-b2ad9c02bda4@ewie.name> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Rspamd-Queue-Id: 4dwPJn48M2z9sq3 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2026-01-20 10:17 +0100, ManiR wrote: > As part of a security documentation update, we are preparing a *Cryptographic > Bill of Materials (CBOM)* to document the cryptographic mechanisms used by > the services deployed in our environment. > > We would like your guidance on the *cryptographic mechanisms used by > PostgreSQL*, including: > > - > > The *types of cryptographic mechanisms* involved (for example, TLS/SSL > for client-server communication, authentication mechanisms, password > hashing, replication security, encryption at rest where applicable) > - > > The *cryptographic algorithms and protocols* used > - > > The *source or storage location* of cryptographic material (for example, > configuration files, certificates, private keys, system catalogs, or > external key management systems) > - > > The *purpose* of each mechanism (for example, data-in-transit > encryption, authentication, access control, replication security) > > Our goal is to accurately document PostgreSQL’s cryptographic controls > for *compliance > and audit purposes*. This request is for documentation clarity only and is *not > related to vulnerability disclosure*. > > Any clarification or references to official PostgreSQL documentation would > be greatly appreciated. Some links to get you going: https://www.postgresql.org/docs/current/encryption-options.html https://www.postgresql.org/docs/current/ssl-tcp.html https://www.postgresql.org/docs/current/gssapi-enc.html https://www.postgresql.org/docs/current/ssh-tunnels.html https://www.postgresql.org/docs/current/client-authentication.html https://www.postgresql.org/docs/current/libpq-ssl.html https://www.postgresql.org/docs/current/sasl-authentication.html https://www.postgresql.org/docs/current/pgcrypto.html -- Erik Wienhold