[MacPorts] #68777: postgresql16 16.1 cannot connect to servers that require SSL since last update

[MacPorts]

#68777: postgresql16 16.1 cannot connect to servers that require SSL since last
update
------------------------+---------------------------------------
 Reporter:  davidnich   |      Owner:  dgilman
     Type:  defect      |     Status:  assigned
 Priority:  Normal      |  Milestone:
Component:  ports       |    Version:  2.8.1
 Keywords:  postgresql  |       Port:  postgresql15 postgresql16
------------------------+---------------------------------------
 After the last update to postgresql15 and postgresql16, I can no longer
 connect to servers that require SSL (with either port).

 I get the following error with `psql` for example:

 {{{
 $ psql -Uqorusapi -hsupah -p31432
 psql: error: connection to server at "supah" (192.168.16.20), port 31432
 failed: FATAL:  no PostgreSQL user name specified in startup packet
 connection to server at "supah" (192.168.16.20), port 31432 failed: FATAL:
 no PostgreSQL user name specified in startup packet
 psql(45426,0x1e07b9ec0) malloc: *** error for object 0x17: pointer being
 freed was not allocated
 psql(45426,0x1e07b9ec0) malloc: *** set a breakpoint in malloc_error_break
 to debug
 zsh: abort      psql -Uqorusapi -hsupah -p31432
 }}}

 This server is running in a `postgres-operator` cluster - from Linux a
 successful connection looks like:
 {{{
 $ psql -Uqorusapi -hsupah -p 31432
 Password for user qorusapi:
 Pager usage is off.
 psql (15.4, server 15.3)
 SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384,
 compression: off)
 Type "help" for help.

 qorusapi=>
 }}}

 Connections to local PostgreSQL DBs and to remote DBs that do not require
 SSL succeed, so my assumption is that something in the last security
 patches affected the ability of these ports to connect to PostgreSQL DBs
 that require SSL.

-- 
Ticket URL: <https://trac.macports.org/ticket/68777>
MacPorts <https://www.macports.org/>
Ports system for macOS