public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Page <[email protected]>
To: Mihailescu, Florin-Catalin <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: support for the certificate signature on the latest 15th pgadmin version
Date: Sat, 23 May 2026 11:54:51 -0700
Message-ID: <CA+OCxozAOYyeJbV4wWQ_EotLMOu3V7NkMjk6Zn6DUMJp3Bz1Vg@mail.gmail.com> (raw)
In-Reply-To: <PAWPR08MB98317C88A5006181B943A5F3EE0F2@PAWPR08MB9831.eurprd08.prod.outlook.com>
References: <PAWPR08MB98317C88A5006181B943A5F3EE0F2@PAWPR08MB9831.eurprd08.prod.outlook.com>
Hi
Yes, it has a new certificate because the old one has expired, as was noted
in the release notes for v9.12:
https://www.pgadmin.org/docs/pgadmin4/9.12/release_notes_9_12.html
Microsoft have changed their requirements for obtaining a certificate for
signing now, such that it is extremely expensive and unfeasible for us to
obtain a high trust certificate like the old EnterpriseDB one. The new one
is an Open Source developer certificate from Certum which is considered low
trust until it gains reputation over time. This may be why your machine is
showing it as invalid, if the machine is configured with very tight
security requirements.
On my machines, it is shown as valid.
[image: Screenshot 2026-05-23 at 11.47.29.png]
Regards, Dave.
On Sat, 23 May 2026 at 11:45, Mihailescu, Florin-Catalin <
[email protected]> wrote:
> Hello,
>
>
>
> I’ve tried to get your lates release for pgadmin. It seems that it has a
> new different signing certificate than the ones before (ex. 11 version)
>
> Could you sign and publish it again, please ?
>
> Thank you.
>
>
>
> The 11 version:
>
>
>
> The 15th version:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Cu Stima,
>
> Kind Regards,
>
> *Mihailescu Catalin*
>
> Expert RPA Service Delivery Management
>
> Advanced Analytics & Automation
>
> Downstream IT & Digitalisation
>
> Divisional IT & Bus. Consulting
>
> ______________________
>
> OMV Petrom Global Solutions SRL
>
> Petrom City, 22 Coralilor Street, Sector 1
>
> Postal Code 013329, Bucharest, Romania
>
>
>
> Mobile : +40 (726) 126198
>
> [email protected]
>
> *http://www.petrom.com <http://www.petrom.com/>* / *http://www.omv.com
> <http://www.omv.com/>*
>
>
>
>
>
> *Respectă şi tu viitorul! Printează acest e-mail doar dacă este necesar.
> /Respect the future! **Print this e-mail only if necessary.*
>
> *OMV Petrom S.A., Petrom City, Strada Coralilor nr. 22, cod postal
> 013329, sector 1, Bucureşti ROMÂNIA, Cod fiscal (tax number): C.I.F. RO 159
> 0082, Nr. Înreg. Registrul Comerţului (reg. no. in Commercial Registry):
> J40/8302/1997*
>
> *Acest mesaj este confidenţial şi adresat exclusiv destinatarului. Dacă
> aţi primit acest mesaj din greşeală, vă rugăm să informaţi imediat
> expeditorul şi să ştergeţi mesajul şi ataşamentele. Vă mulţumim. În
> condiţiile prevăzute de lege, OMV Petrom nu va fi răspunzător pentru
> daunele, oricare ar fi natura acestora, care decurg din transmiterea de
> erori, viruşi, influenţe externe, întârzieri şi alte elemente similare. *
>
>
>
> *This message is confidential and intended solely for the addressee. If
> you receive this message in error, please immediately inform the sender and
> delete the message and any attachments. Thank you. To the extent permitted
> by law, OMV Petrom shall in no way be liable for any damages, whatever
> their nature, arising out of transmission failures, viruses, external
> influence, delays and the like.*
>
>
>
> Internal
>
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
Attachments:
[image/png] image001.png (227.8K, 3-image001.png)
download | view image
[image/png] image002.png (147.3K, 4-image002.png)
download | view image
[image/png] Screenshot 2026-05-23 at 11.47.29.png (225.6K, 5-Screenshot%202026-05-23%20at%2011.47.29.png)
download | view image
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: support for the certificate signature on the latest 15th pgadmin version
In-Reply-To: <CA+OCxozAOYyeJbV4wWQ_EotLMOu3V7NkMjk6Zn6DUMJp3Bz1Vg@mail.gmail.com>
* 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