| From: | sutyak <sutyak(at)proton(dot)me> |
|---|---|
| To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | PostgreSQL 18 FIPS mode in Windows |
| Date: | 2026-09-24 20:07:48 |
| Message-ID: | 13DyT-dt7PRebAXIz_sNbi_b620YX_uKUa-PhyJeyx2wAEV_R-ECdopU7jCioVHbhQx_oG-Ne18GP2CJEnVYRLsvMenSM5QN23gssgsYuoU=@proton.me |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I have previously been compiling my own FIPS-compliant PostgreSQL and OpenSSL in Windows for FIPS compliance, but the documentation for 18 makes it sound like it is ready out of the box, and it would certainly be nice to just grab the latest off the shelf installer and use it.
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,
Mark Sutyak
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-09-24 20:13:21 | Re: PostgreSQL 18 FIPS mode in Windows |
| Previous Message | Adrian Klaver | 2026-09-24 15:01:26 | Re: Multiple schemas |