Opened 12 months ago
Last modified 12 months ago
#68791 closed defect
openssl 3.2.0 incompatible with psql — at Initial Version
Reported by: | jrabinow | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | neverpanic (Clemens Lang) | |
Port: | openssl3, postgresql16 |
Description
$ psql service=localdb psql (16.1) Type "help" for help. localhost/localdb=> \q
$ psql service=remotedb psql: error: connection to server at "remotedb.rds.amazonaws.com" (10.0.0.1), port 5432 failed: FATAL: no PostgreSQL user name specified in startup packet connection to server at "remotedb.rds.amazonaws.com" (10.0.0.1), port 5432 failed: FATAL: no PostgreSQL user name specified in startup packet psql(18855,0x1e2cfdec0) malloc: *** error for object 0xa3: pointer being freed was not allocated psql(18855,0x1e2cfdec0) malloc: *** set a breakpoint in malloc_error_break to debug Abort trap: 6 [Exit 134 (ABRT)]
I chanced upon this stack overflow response and gave reverting commit 95984554 a shot. Results show that neither psql13 nor psql16 can run with openssl3@3.2.0, while both run fine with openssl3@3.1.4
This might be reported upstream, I'm not sure whether with the openssl or the postgresql folks, but I wanted to open a bug here against openssl3 port since this port update triggered the breakage.
Note: See
TracTickets for help on using
tickets.