Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nFQzM-0003a5-Jd for pgsql-bugs@arkaria.postgresql.org; Thu, 03 Feb 2022 01:32:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nFQyo-0000AD-B8 for pgsql-bugs@arkaria.postgresql.org; Thu, 03 Feb 2022 01:32:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nFQyo-0000A0-2t for pgsql-bugs@lists.postgresql.org; Thu, 03 Feb 2022 01:32:10 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nFQyh-0000Ap-7P for pgsql-bugs@lists.postgresql.org; Thu, 03 Feb 2022 01:32:08 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 2131Vq0h131330; Wed, 2 Feb 2022 20:31:52 -0500 From: Tom Lane To: Thomas Munro cc: Andres Freund , byavuz81@gmail.com, PostgreSQL mailing lists , Heikki Linnakangas , Michael Paquier Subject: Re: BUG #17391: While using --with-ssl=openssl and PG_TEST_EXTRA='ssl' options, SSL tests fail on OpenBSD 7.0 In-reply-to: References: <17391-304f81bcf724b58b@postgresql.org> <20220202213900.h7paogmcge2rtls6@alap3.anarazel.de> Comments: In-reply-to Thomas Munro message dated "Thu, 03 Feb 2022 13:42:34 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <131328.1643851912.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 02 Feb 2022 20:31:52 -0500 Message-ID: <131329.1643851912@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > Anyway, I can also reproduce this problem on my Vagrant image (OpenBSD > 6.9 'cause I haven't got around to setting up 7). I had an OpenBSD 6.8 image laying about, so I tried the ssl test there, and it falls over in even more places: Test Summary Report ------------------- t/001_ssltests.pl (Wstat: 8448 Tests: 110 Failed: 33) Failed tests: 14, 16, 18-20, 28, 30-32, 58, 60, 72-76 79-83, 88-90, 94-95, 97, 99, 102, 104, 106 108, 110 Non-zero exit status: 33 t/002_scram.pl (Wstat: 1792 Tests: 11 Failed: 7) Failed tests: 1, 4-5, 7, 9-11 Non-zero exit status: 7 t/003_sslinfo.pl (Wstat: 7424 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 29 Parse errors: Bad plan. You planned 13 tests but ran 1. A lot of the errors look like they didn't yet have support for TLS 1.2; this is typical: # Failed test 'pg_stat_ssl with client certificate: no stderr' # at t/001_ssltests.pl line 523. # got: 'psql: error: connection to server at "127.0.0.1", port 57= 105 failed: SSL error: tlsv1 alert protocol version # This may indicate that the server does not support any SSL protocol vers= ion between TLSv1.2 and TLSv1.2. The postmaster log entries corresponding to this look like 2022-02-02 20:13:49.420 EST [16352] [unknown] LOG: connection received: h= ost=3Dlocalhost port=3D39596 2022-02-02 20:13:49.429 EST [16352] [unknown] LOG: could not accept SSL c= onnection: sslv3 alert illegal parameter I don't see anything in /etc/ssl/openssl.cnf that looks related to TLS protocol restrictions. Perhaps 6.8 is too old to be of interest anymore, but that's what I've got handy. BTW, I also reproduced something that seems odd from the OP's postmaster logs: there are what seem a quite excessive number of checkpoints happening during these tests. That happens on my Linux box too, so it's not an OpenBSD issue. It looks like there are two per CREATE DATABASE --- I could understand one maybe, but why two? regards, tom lane