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 1jovt2-0007Nh-U9 for pgsql-hackers@arkaria.postgresql.org; Fri, 26 Jun 2020 21:27:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jovt1-0003cf-QS for pgsql-hackers@arkaria.postgresql.org; Fri, 26 Jun 2020 21:27:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jovt1-0003cY-JW for pgsql-hackers@lists.postgresql.org; Fri, 26 Jun 2020 21:27:51 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jovsz-0003qj-06 for pgsql-hackers@postgresql.org; Fri, 26 Jun 2020 21:27:51 +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 05QLRi2D031489; Fri, 26 Jun 2020 17:27:44 -0400 From: Tom Lane To: Daniel Gustafsson cc: Magnus Hagander , Peter Eisentraut , pgsql-hackers Subject: Re: should libpq also require TLSv1.2 by default? In-reply-to: <0817C931-564B-4DFF-921C-90915889F451@yesql.se> References: <4FBC50DB-599A-42AA-90C8-3051E3A748BB@yesql.se> <2305871.1593125045@sss.pgh.pa.us> <2339796.1593177583@sss.pgh.pa.us> <16724.1593185802@sss.pgh.pa.us> <29049.1593202957@sss.pgh.pa.us> <0817C931-564B-4DFF-921C-90915889F451@yesql.se> Comments: In-reply-to Daniel Gustafsson message dated "Fri, 26 Jun 2020 23:18:58 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <31487.1593206864.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 26 Jun 2020 17:27:44 -0400 Message-ID: <31488.1593206864@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Daniel Gustafsson writes: > SSL_R_UNKNOWN_PROTOCOL seem to covers cases when someone manages to perf= orm > something which OpenSSL believes is a broken SSLv2 connection, but their= own > client-level code use it to refer to SSL as well as TLS. Maybe it's wor= th > adding as a belts and suspenders type thing? No objection on my part. > Is this targeting v13 or v14? In case of the former, the release notes = entry > for raising the default minimum version should perhaps be tweaked as it = now > just refers to the GUC which is a tad misleading. I think Peter is proposing that we change this in v13. I didn't look at the release notes; usually we cover this sort of thing in-bulk when we update the release notes later in beta. > If anything it might useful to document in the comment that we're only > concerned with TLS versions, SSL2/3 are disabled in the library initiali= zation. Good point. regards, tom lane