This message and any attachments may contain confidential material and information and are intended only for the use of the intended recipient(s). If you are not the person to whom this message is addressed, be aware that any use, reproduction, or distribution of this message is strictly prohibited. If you received this in error, please contact the sender and immediately delete this email and any attachments.
From: Daniel Gustafsson <daniel@yesql.se> Date: Tuesday, February 18, 2025 at 6:49AM To: Moore, David A <MOOREDA9@gru.com> Cc: pgsql-odbc@postgresql.org <pgsql-odbc@postgresql.org>, LeMaster, James C <LeMasterJC@gru.com>, Gause Jr, George <GauseG1@gru.com> Subject: [EXTERNAL] Re: Hash Value for Updated POSTGRESQL?
> On 14 Feb 2025, at 20:33, Moore, David A <MOOREDA9@gru.com> wrote: > > Hello, We are a NERC regulated organization in the critical infrastructure arena. The most recent zero-day injection bug (CVE-2025-1094) has us concerned. We are attempting to update our postgresql, which has several dependencies in our organization. We are failing to find a md5 to verify authenticity and perform an integrity check on the installation file. I have researched this and finding nothing on this topic except for other orgs finding the same issues. Can you please advise us on this and any method of verification that you may provide that will satisfy our stringent compliance requirements?
First of all, you are emailing the discussion list for the postgres ODBC driver but reading your email I'm fairly sure you mean the postgres server and not the ODBC driver.
Regarding package signatures, the postgres project only offers source core downloads and for those hash fingerprints are available. See for example the 17.3 version:
