Message-ID: <gh-postgresql-interfaces-psqlodbc-168@github.com>
From: "crea-bank (@crea-bank)" <noreply+crea-bank@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Tue, 31 Mar 2026 11:58:56 +0000
Subject: [postgresql-interfaces/psqlodbc] issue #168: OpenSSL EOL in Windows builds → request for 3.5 LTS adoption (compliance impact)
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Id: 272509141
X-GitHub-Author-Login: crea-bank
X-GitHub-Issue: 168
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-State: closed
X-GitHub-Type: issue
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/issues/168
Content-Type: text/plain; charset=utf-8

Current Windows builds of psqlODBC appear to ship with OpenSSL 3.3.x, which reaches end of life in April 2026.

This causes issues in enterprise environments:

Security scanners flag the bundled OpenSSL as EOL / unsupported
Leads to audit findings (e.g. ISO 27001, internal policies)
Can become a deployment blocker

Upgrading to short-lived versions (e.g. 3.4.x) would only be a temporary fix.

Since OpenSSL 3.5 is now the LTS release (supported until 2030), it would be preferable to move directly to 3.5 in Windows builds.

Questions:

Are there plans to adopt OpenSSL 3.5 LTS?
Is there an expected timeline?

Thanks for your work on psqlODBC!