From: Tom Lane <tgl@sss.pgh.pa.us>
To: tommi.pakarinen@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19050: psql: could not find digest for NID UNDEF
In-reply-to: <19050-b7fc71875d64588a@postgresql.org>
References: <19050-b7fc71875d64588a@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 11 Sep 2025 13:23:05 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1783658.1757602842.1@sss.pgh.pa.us>
Date: Thu, 11 Sep 2025 11:00:42 -0400
Message-ID: <1783659.1757602842@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1783659.1757602842%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> When Ed25519 certificate is configured on PG server, I'm able to connect
> with a Java client. Also, openssl and sslscan were able make connection and
> show certificate details. Still CLI tool (psql) does not work with it and
> refuses to connect.

This does look similar to the previous discussion about RSA-PSS.
But we fixed that a couple years ago.  Are you sure your libpq
is up-to-date?  What about the openssl libraries it's bound to?

> $ openssl version
> OpenSSL 3.2.2 4 Jun 2024 (Library: OpenSSL 3.2.2 4 Jun 2024)

This proves zero about what libpq is using.  Applying "ldd"
to psql might be more enlightening.

			regards, tom lane