From: Tom Lane <tgl@sss.pgh.pa.us>
To: sutyak <sutyak@proton.me>
cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: PostgreSQL 18 FIPS mode in Windows
In-reply-to: 
 <13DyT-dt7PRebAXIz_sNbi_b620YX_uKUa-PhyJeyx2wAEV_R-ECdopU7jCioVHbhQx_oG-Ne18GP2CJEnVYRLsvMenSM5QN23gssgsYuoU=@proton.me>
References: 
 <13DyT-dt7PRebAXIz_sNbi_b620YX_uKUa-PhyJeyx2wAEV_R-ECdopU7jCioVHbhQx_oG-Ne18GP2CJEnVYRLsvMenSM5QN23gssgsYuoU=@proton.me>
Comments: In-reply-to sutyak <sutyak@proton.me>
	message dated "Thu, 24 Sep 2026 20:07:48 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1814988.1790280801.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 24 Sep 2026 16:13:21 -0400
Message-ID: <1814989.1790280801@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1814989.1790280801%40sss.pgh.pa.us>
Precedence: bulk

sutyak <sutyak@proton.me> writes:
> The steps I have already taken are:

> - Install PostgreSQL 18.6 windows-x64
> - Install OpenSSL 3.5.8 with FIPS Provider 3.1.2
> - Enable pgcrypto extension via pgAdmin
> - set builtin_crypto_enabled to 'fips'
> - Executing SELECT fips_mode(); always returns false.
> - Verified FIPS is not being enforced by executing SELECT encode(digest(=
'test', 'md5'), 'hex'); and it always returns a value.

> What am I missing? Thank you,

'builtin_crypto_enabled =3D fips' merely tells pgcrypto to expect
failure of relevant calls.  It does not cause OpenSSL to actually
go into FIPS mode.  You'd have to consult the OpenSSL docs to
find out how to do that.

			regards, tom lane