| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Kishore Isaac <k(dot)isaac(at)loccioni(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Tenable Report Issue even after upgrading to correct Postgres version |
| Date: | 2021-11-11 17:48:39 |
| Message-ID: | 20211111174839.GB8669@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Nov 11, 2021 at 03:49:29PM +0000, Kishore Isaac wrote:
> To Whom It May Concern:
>
>
>
> We were informed by a customer using Tenable reports that we needed to upgrade
> Postgres from 12.2 to 12.7 due to vulnerability issues. We have since upgraded
> to the requested version of Postgres (12.7) but the Tenable report scans still
> show that the version is 12.2. After reaching out the Tenable, we found that
> the version information is not updated in the system registry where Tenable is
> pulling the information from. Is there any resolution for this?
>
>
>
> Below is the registry information:
Uh, I have no idea what Tenable is, which I think means we don't control
that way of distributing Postgres.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-11-11 17:54:43 | Re: Tenable Report Issue even after upgrading to correct Postgres version |
| Previous Message | Kishore Isaac | 2021-11-11 15:49:29 | Tenable Report Issue even after upgrading to correct Postgres version |