postgresql-interfaces/psqlodbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: crea-bank (@crea-bank) <[email protected]>
To: postgresql-interfaces/psqlodbc <[email protected]>
Subject: [postgresql-interfaces/psqlodbc] issue #168: OpenSSL EOL in Windows builds → request for 3.5 LTS adoption (compliance impact)
Date: Tue, 31 Mar 2026 11:58:56 +0000
Message-ID: <[email protected]> (raw)

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!

view thread (3+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://postgresql-interfaces/psqlodbc
  Cc: [email protected], [email protected]
  Subject: Re: [postgresql-interfaces/psqlodbc] issue #168: OpenSSL EOL in Windows builds → request for 3.5 LTS adoption (compliance impact)
  In-Reply-To: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox