Re: Hash Value for Updated POSTGRESQL?

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: "Moore, David A" <MOOREDA9(at)gru(dot)com>
Cc: "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>, "LeMaster, James C" <LeMasterJC(at)gru(dot)com>, "Gause Jr, George" <GauseG1(at)gru(dot)com>
Subject: Re: Hash Value for Updated POSTGRESQL?
Date: 2025-02-18 11:49:21
Message-ID: 2D4A1EED-E6AD-4AD9-BDD2-CCA07847CF68@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> On 14 Feb 2025, at 20:33, Moore, David A <MOOREDA9(at)gru(dot)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:

https://www.postgresql.org/ftp/source/v17.3/

If you download a pre-built package or installer you need to check with whom it
is you are downloading from.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Moore, David A 2025-02-18 13:07:24 Re: [EXTERNAL] Re: Hash Value for Updated POSTGRESQL?
Previous Message Moore, David A 2025-02-14 19:33:27 Hash Value for Updated POSTGRESQL?