Hello pgAdmin Team,

I would like to report what appears to be a packaging/signing issue with
the official *pgAdmin 9.16 x64 macOS DMG*.
Environment

   - *pgAdmin:* 9.16 (official x64 DMG downloaded from the pgAdmin website)
   - *macOS:* Sonoma 14.8.7
   - *Architecture:* Intel (x86_64)
   - *Installation:* Fresh macOS installation

Initial Issue

Immediately after launching pgAdmin, the application fails to start with
the following error:

ImportError: dlopen(.../_rust.abi3.so): Library not loaded:
/usr/local/opt/openssl@3/lib/libssl.3.dylib

Running otool -L on the bundled cryptography extension shows:

/usr/local/opt/openssl@3/lib/libssl.3.dylib
/usr/local/opt/openssl@3/lib/libcrypto.3.dylib

This indicates that _rust.abi3.so is linked against a Homebrew OpenSSL
installation.
Bundled Libraries

However, the application already contains the required OpenSSL libraries:

Contents/Frameworks/libssl.3.dylib
Contents/Frameworks/libcrypto.3.dylib
Contents/Frameworks/Python.framework/Versions/3.13/lib/libssl.3.dylib
Contents/Frameworks/Python.framework/Versions/3.13/lib/libcrypto.3.dylib

The bundled libssl.3.dylib itself appears to be correctly linked using
@rpath rather than an absolute Homebrew path.
Additional Testing

I installed Homebrew and openssl@3, after which the error changed to:

code signature ... not valid for use in process:
mapping process and mapped file (non-platform) have different Team IDs

This suggests that macOS Library Validation is rejecting the external
Homebrew OpenSSL library, which is expected for a hardened application.

I also attempted to modify _rust.abi3.so using install_name_tool so it
referenced the bundled OpenSSL libraries instead of /usr/local/opt/openssl@3.
After re-signing the application, startup progressed further but failed
with another Library Validation error involving the bundled Python
framework:

dyld: Library not loaded: @rpath/Versions/3.13/Python
Reason: code signature ... mapping process and mapped file
(non-platform) have different Team IDs

Observations

>From my investigation, it appears that:

   - _rust.abi3.so is linked against an external Homebrew OpenSSL
   installation rather than the bundled libraries.
   - The application already includes the required OpenSSL libraries.
   - The issue appears to affect the official Intel (x64) macOS package.
   - This occurs on a clean installation of macOS Sonoma 14.8.7.

Could you please verify whether the Intel macOS build was packaged with
incorrect library references or code-signing metadata?

Thank you for your time and for maintaining pgAdmin.

Best regards,

Octavianus Bramantya

Reply via email to