Thread: pgAdmin 4 v4.26 released
The pgAdmin Development Team is pleased to announce pgAdmin 4 version 4.26.
This release of pgAdmin 4 includes 30 bug fixes and new features. For more details please see the release notes at:
https://www.pgadmin.org/docs/pgadmin4/4.26/release_notes_4_26.html.
This release of pgAdmin 4 includes 30 bug fixes and new features. For more details please see the release notes at:
https://www.pgadmin.org/docs/pgadmin4/4.26/release_notes_4_26.html.
pgAdmin is the leading Open Source graphical management tool for PostgreSQL. For more information, please see:
https://www.pgadmin.org/
Notable changes in this release include:
https://www.pgadmin.org/
Notable changes in this release include:
- Added SQL Formatter support in Query Tool.
- Added a new button to the query tool toolbar to open a new query tool window.
- Added shared server support for admin users.
- Warn the user when connecting to a server that is older than pgAdmin supports.
- Ensure that schema names starting with 'pg' should be visible in the browser tree when standard_conforming_strings is set to off.
- Fixed an issue where --load-server does not allow loading connections that use pg_services.
- Fixed string indices must be integers issue for PostgreSQL < 9.3.
- Fixed an issue where the application ignores the fixed port configuration value.
- Remove the illegal argument from the trigger function in the trigger DDL statement.
- Ensure that 'setup-web.sh' should work in Debian 10.
- Fixed excessive CPU usage by stopping the indefinite growth of the graph dataset.
Builds for Windows and macOS are available now, along with a Python Wheel,
Docker Container, RPM, DEB Package, and source code tarball from:
Docker Container, RPM, DEB Package, and source code tarball from:
--
Akshay Joshi
pgAdmin Project
Akshay,
Just downloaded pgadmin4-4.26-x64.exe from the official web site. When I go to install it comes up with an "unknown publisher".
Is this legit?
Thanks,
rik.
On Thu, Sep 17, 2020 at 8:09 AM Akshay Joshi <akshay.joshi@enterprisedb.com> wrote:
The pgAdmin Development Team is pleased to announce pgAdmin 4 version 4.26.
This release of pgAdmin 4 includes 30 bug fixes and new features. For more details please see the release notes at:
https://www.pgadmin.org/docs/pgadmin4/4.26/release_notes_4_26.html.pgAdmin is the leading Open Source graphical management tool for PostgreSQL. For more information, please see:
https://www.pgadmin.org/
Notable changes in this release include:
- Added SQL Formatter support in Query Tool.
- Added a new button to the query tool toolbar to open a new query tool window.
- Added shared server support for admin users.
- Warn the user when connecting to a server that is older than pgAdmin supports.
- Ensure that schema names starting with 'pg' should be visible in the browser tree when standard_conforming_strings is set to off.
- Fixed an issue where --load-server does not allow loading connections that use pg_services.
- Fixed string indices must be integers issue for PostgreSQL < 9.3.
- Fixed an issue where the application ignores the fixed port configuration value.
- Remove the illegal argument from the trigger function in the trigger DDL statement.
- Ensure that 'setup-web.sh' should work in Debian 10.
- Fixed excessive CPU usage by stopping the indefinite growth of the graph dataset.
Builds for Windows and macOS are available now, along with a Python Wheel,
Docker Container, RPM, DEB Package, and source code tarball from:--Akshay JoshipgAdmin Project
On Thu, Sep 17, 2020 at 4:18 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:
Akshay,Just downloaded pgadmin4-4.26-x64.exe from the official web site. When I go to install it comes up with an "unknown publisher".Is this legit?
I'm seeing that too - there doesn't seem to be a digital signature on the installer.
I have to wonder a) how that happened without the build failing, and b) how it got past QA?
Hi
On Thu, Sep 17, 2020 at 4:22 PM Dave Page <dpage@pgadmin.org> wrote:
On Thu, Sep 17, 2020 at 4:18 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:Akshay,Just downloaded pgadmin4-4.26-x64.exe from the official web site. When I go to install it comes up with an "unknown publisher".Is this legit?I'm seeing that too - there doesn't seem to be a digital signature on the installer.
So to the original question, yes, it is legit. The certificate expired :-(
I have to wonder a) how that happened without the build failing,
That happened because all our build scripts will ignore certificate not found type errors, throwing out a warning to the (very long) build log instead. Microsoft's tools don't give a separate error for expired certificates - they have a generic "No suitable certificate found" one.
It does it that way because individual developers don't have code signing certificates (they're expensive, a pain to get, and we don't want random ones with our name on them in existence, or to have lots of people with access to the one we use). Obviously the developers need to be able to build, even though they don't have a CSC.
Dave,
Thanks for the update. Are you going to rerelease the update with a valid certificate, or at least publish the SHA256 hash for the file so that we can verify that it downloaded correctly?
Thanks again,
rik.
On Fri, Sep 18, 2020 at 4:45 AM Dave Page <dpage@pgadmin.org> wrote:
Hi--On Thu, Sep 17, 2020 at 4:22 PM Dave Page <dpage@pgadmin.org> wrote:On Thu, Sep 17, 2020 at 4:18 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:Akshay,Just downloaded pgadmin4-4.26-x64.exe from the official web site. When I go to install it comes up with an "unknown publisher".Is this legit?I'm seeing that too - there doesn't seem to be a digital signature on the installer.So to the original question, yes, it is legit. The certificate expired :-(I have to wonder a) how that happened without the build failing,That happened because all our build scripts will ignore certificate not found type errors, throwing out a warning to the (very long) build log instead. Microsoft's tools don't give a separate error for expired certificates - they have a generic "No suitable certificate found" one.It does it that way because individual developers don't have code signing certificates (they're expensive, a pain to get, and we don't want random ones with our name on them in existence, or to have lots of people with access to the one we use). Obviously the developers need to be able to build, even though they don't have a CSC.
I would 100% expect that that a certificate issue would lead to a priority out of schedule release, in this case a 4.26.1 or 4.26.0.1 as the case may be, its actually a major issue when security mechanisms are flagging a legit publication as not legit, you do NOT want users making security exceptions for your software. -- Darren Duncan On 2020-09-18 4:59 p.m., richard coleman wrote: > Dave, > > Thanks for the update. Are you going to rerelease the update with a valid > certificate, or at least publish the SHA256 hash for the file so that we can > verify that it downloaded correctly? > > Thanks again, > > rik.
On Sat, 19 Sep 2020 at 00:59, richard coleman <rcoleman.ascentgl@gmail.com> wrote:
Dave,Thanks for the update. Are you going to rerelease the update with a valid certificate, or at least publish the SHA256 hash for the file so that we can verify that it downloaded correctly?
Yes, a new release is in progress already.
Thanks again,rik.On Fri, Sep 18, 2020 at 4:45 AM Dave Page <dpage@pgadmin.org> wrote:Hi--On Thu, Sep 17, 2020 at 4:22 PM Dave Page <dpage@pgadmin.org> wrote:On Thu, Sep 17, 2020 at 4:18 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:Akshay,Just downloaded pgadmin4-4.26-x64.exe from the official web site. When I go to install it comes up with an "unknown publisher".Is this legit?I'm seeing that too - there doesn't seem to be a digital signature on the installer.So to the original question, yes, it is legit. The certificate expired :-(I have to wonder a) how that happened without the build failing,That happened because all our build scripts will ignore certificate not found type errors, throwing out a warning to the (very long) build log instead. Microsoft's tools don't give a separate error for expired certificates - they have a generic "No suitable certificate found" one.It does it that way because individual developers don't have code signing certificates (they're expensive, a pain to get, and we don't want random ones with our name on them in existence, or to have lots of people with access to the one we use). Obviously the developers need to be able to build, even though they don't have a CSC.
On Sat, Sep 19, 2020 at 7:21 AM Dave Page <dpage@pgadmin.org> wrote:
On Sat, 19 Sep 2020 at 00:59, richard coleman <rcoleman.ascentgl@gmail.com> wrote:Dave,Thanks for the update. Are you going to rerelease the update with a valid certificate, or at least publish the SHA256 hash for the file so that we can verify that it downloaded correctly?Yes, a new release is in progress already.
I came to the conclusion that a new release isn't warranted, as there are no code changes, or any changes to the package contents at all; instead I have manually signed the original installers on the build server, and then re-pushed to the download site.
Apologies for any inconvenience.
--Thanks again,rik.On Fri, Sep 18, 2020 at 4:45 AM Dave Page <dpage@pgadmin.org> wrote:Hi--On Thu, Sep 17, 2020 at 4:22 PM Dave Page <dpage@pgadmin.org> wrote:On Thu, Sep 17, 2020 at 4:18 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:Akshay,Just downloaded pgadmin4-4.26-x64.exe from the official web site. When I go to install it comes up with an "unknown publisher".Is this legit?I'm seeing that too - there doesn't seem to be a digital signature on the installer.So to the original question, yes, it is legit. The certificate expired :-(I have to wonder a) how that happened without the build failing,That happened because all our build scripts will ignore certificate not found type errors, throwing out a warning to the (very long) build log instead. Microsoft's tools don't give a separate error for expired certificates - they have a generic "No suitable certificate found" one.It does it that way because individual developers don't have code signing certificates (they're expensive, a pain to get, and we don't want random ones with our name on them in existence, or to have lots of people with access to the one we use). Obviously the developers need to be able to build, even though they don't have a CSC.
Dave,
Could you please confirm that the issue only affects the Windows install and not the other ways of setting up pgAdmin.
My team is relying on the Python Wheel setup we run on Linux.
Thank you.
On Mon, Sep 21, 2020 at 6:09 AM Dave Page <dpage@pgadmin.org> wrote:
On Sat, Sep 19, 2020 at 7:21 AM Dave Page <dpage@pgadmin.org> wrote:On Sat, 19 Sep 2020 at 00:59, richard coleman <rcoleman.ascentgl@gmail.com> wrote:Dave,Thanks for the update. Are you going to rerelease the update with a valid certificate, or at least publish the SHA256 hash for the file so that we can verify that it downloaded correctly?Yes, a new release is in progress already.I came to the conclusion that a new release isn't warranted, as there are no code changes, or any changes to the package contents at all; instead I have manually signed the original installers on the build server, and then re-pushed to the download site.Apologies for any inconvenience.--Thanks again,rik.On Fri, Sep 18, 2020 at 4:45 AM Dave Page <dpage@pgadmin.org> wrote:Hi--On Thu, Sep 17, 2020 at 4:22 PM Dave Page <dpage@pgadmin.org> wrote:On Thu, Sep 17, 2020 at 4:18 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:Akshay,Just downloaded pgadmin4-4.26-x64.exe from the official web site. When I go to install it comes up with an "unknown publisher".Is this legit?I'm seeing that too - there doesn't seem to be a digital signature on the installer.So to the original question, yes, it is legit. The certificate expired :-(I have to wonder a) how that happened without the build failing,That happened because all our build scripts will ignore certificate not found type errors, throwing out a warning to the (very long) build log instead. Microsoft's tools don't give a separate error for expired certificates - they have a generic "No suitable certificate found" one.It does it that way because individual developers don't have code signing certificates (they're expensive, a pain to get, and we don't want random ones with our name on them in existence, or to have lots of people with access to the one we use). Obviously the developers need to be able to build, even though they don't have a CSC.--
On Mon, Sep 21, 2020 at 5:56 PM Cherio <cherio@gmail.com> wrote:
Dave,Could you please confirm that the issue only affects the Windows install and not the other ways of setting up pgAdmin.My team is relying on the Python Wheel setup we run on Linux.
Yes it only affected Windows, and even then it wouldn't have stopped it working.
Thank you.On Mon, Sep 21, 2020 at 6:09 AM Dave Page <dpage@pgadmin.org> wrote:On Sat, Sep 19, 2020 at 7:21 AM Dave Page <dpage@pgadmin.org> wrote:On Sat, 19 Sep 2020 at 00:59, richard coleman <rcoleman.ascentgl@gmail.com> wrote:Dave,Thanks for the update. Are you going to rerelease the update with a valid certificate, or at least publish the SHA256 hash for the file so that we can verify that it downloaded correctly?Yes, a new release is in progress already.I came to the conclusion that a new release isn't warranted, as there are no code changes, or any changes to the package contents at all; instead I have manually signed the original installers on the build server, and then re-pushed to the download site.Apologies for any inconvenience.--Thanks again,rik.On Fri, Sep 18, 2020 at 4:45 AM Dave Page <dpage@pgadmin.org> wrote:Hi--On Thu, Sep 17, 2020 at 4:22 PM Dave Page <dpage@pgadmin.org> wrote:On Thu, Sep 17, 2020 at 4:18 PM richard coleman <rcoleman.ascentgl@gmail.com> wrote:Akshay,Just downloaded pgadmin4-4.26-x64.exe from the official web site. When I go to install it comes up with an "unknown publisher".Is this legit?I'm seeing that too - there doesn't seem to be a digital signature on the installer.So to the original question, yes, it is legit. The certificate expired :-(I have to wonder a) how that happened without the build failing,That happened because all our build scripts will ignore certificate not found type errors, throwing out a warning to the (very long) build log instead. Microsoft's tools don't give a separate error for expired certificates - they have a generic "No suitable certificate found" one.It does it that way because individual developers don't have code signing certificates (they're expensive, a pain to get, and we don't want random ones with our name on them in existence, or to have lots of people with access to the one we use). Obviously the developers need to be able to build, even though they don't have a CSC.--