Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iEiur-0006NJ-Ce for pgsql-committers@arkaria.postgresql.org; Sun, 29 Sep 2019 23:47:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iEiup-0007PB-5v for pgsql-committers@arkaria.postgresql.org; Sun, 29 Sep 2019 23:47:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iEiuo-0007Oi-2v for pgsql-committers@lists.postgresql.org; Sun, 29 Sep 2019 23:47:46 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iEiui-0001wM-Eb for pgsql-committers@lists.postgresql.org; Sun, 29 Sep 2019 23:47:45 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id F3CBA21731; Sun, 29 Sep 2019 19:47:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 29 Sep 2019 19:47:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=CiYZe97qnxCnhaZSUR2l1bPge2O fnGIaZpOB/UBft+c=; b=L7ALjm6LqJhHf1NlV1OHQiH3OhXhGIOymDDK05l8xGm q+FxqG6i8iTh8RJHGK9/O7nyzipWBgEgapBLNFiWRd6jEPsvnd/OnHHuqsuTxh0o 42dwd8fH6NwGHaNaUGu5IW0hTI4glvwKYQLvuTlL/sSkwidFLfjC3PaBOdDnBm/J c7KaH0AayGDpO3drZBjV+itYOvAmWOhcK5brTp9rQ4WgY59Erng+NmfwiqI+b4Lj EM3367wcREyLVBxflbjIC78p+hBCwXH44AdruEsikBsP9bwBwAgiiBN50DQV8VOK O/FVmeFyegD+HfV49lCseWP4+dxtRkyxWrcVFq5a0fA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=CiYZe9 7qnxCnhaZSUR2l1bPge2OfnGIaZpOB/UBft+c=; b=zUU1kwecn4PMIJe7Jwhpkt QnQpRMuIjg2n3Rfee+cQFBBbIC4VsaGVJNpHICagt5FtYvkvDoULP3ILUnLS7Lvg H9hMVdJlyUAddC7A0BdLkyUiWbwTFxGh22R732U9vTxMzq3u95blZQ1p1pmFmm4w 8MQ4d+FkKZaivwzQOBc5N560AoKtwx8nRRdppR0buYAGDt6wpeMD10s8x+vcg9qo m/R0Sxjfnk/3mlRFgD94XnSf46C0fBztvkxsfyjrPBM3z26A5RlkngCVS5OIgUGE Gij9bOq9Gct2dqQFX0Fb/hDPh1hZf2qtzj9cLpzi3e8asVp/3rB6/64p5JgB+Rqg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrgedugddvhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdefhedmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddv necuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqh huihgvrhdrgiihiieqnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenucfk phepudduuddruddtvddrudektddrudekheenucfrrghrrghmpehmrghilhhfrhhomhepmh hitghhrggvlhesphgrqhhuihgvrhdrgiihiienucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id D344580066; Sun, 29 Sep 2019 19:47:36 -0400 (EDT) Date: Mon, 30 Sep 2019 08:47:33 +0900 From: Michael Paquier To: Tom Lane Cc: Jeff Davis , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Add libpq parameter 'channel_binding'. Message-ID: <20190929234733.GA2888@paquier.xyz> References: <24857.1569775891@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <24857.1569775891@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 29, 2019 at 12:51:31PM -0400, Tom Lane wrote: > I found out the hard way that the added ssl tests fall over on a > platform that doesn't HAVE_X509_GET_SIGNATURE_NID: > > [...] >=20 > I don't think that it's acceptable for the test to fail on a platform > that we're willing to compile on. Maybe just skip these tests if we > lack X509_get_signature_nid? Yes, that's the bug I found three days ago for which I have posted a patch here: https://www.postgresql.org/message-id/20190927024457.GA8485@paquier.xyz In short, I think that the proper way is to adapt the test if X509_get_signature_nid is not around. > Another point is that this error message is misleading --- or at least > would be misleading if the server had X509_get_signature_nid and the > client didn't. > > -#ifdef HAVE_PGTLS_GET_PEER_CERTIFICATE_HASH > if (conn->channel_binding[0] !=3D 'd') /* disable */ > + { > +#ifdef HAVE_PGTLS_GET_PEER_CERTIFICATE_HASH > selected_mechanism =3D SCRAM_SHA_256_PLUS_NAME; > +#else > + printfPQExpBuffer(&conn->errorMessage, > + libpq_gettext("client does not supp= ort SCRAM-SHA-256-PLUS authentication\n")); > + goto error; > + } > #endif > } Yes, it looks sensible to do that. -- Michael --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl2RQpUACgkQnvQgOdby QH1ctw//Sb/dqlECRiv4xuWjtR3NXeiWSzmXv7/uwHnFDSCVf7qk+S4hdIjq/3mG R5SBpfug3EIvh+Aqx4dfcddbAF6uvkoqT9Q1kcBgpgjat87GJEi/zOrLiXADGtww PzuZJxrhcrf695tsTA8y8tYaf2WfUsEBGfZkz/zsyZKMMF967gEiCk9hehM94SS5 vdYp6aZR2UniyYUmPswaWrq9FurD/DbrwellQIa4U8bgqQRg1mvFoS5dksFCznyI xmIDtHLuyVeXcgHBfuPqQ6XxuTOghWiB9jZCJy5SiBFPQDrA3EjbG13aFlVXg4MO 8VCYErDODV1PbJwzUb5CQtOYlFPsdtFU8zInzxdy2SPoM7SXAdaH8Z5LVEP9RHNl Ue4AkhpEXn7RmCtsEaQEuFojoV/lIh1azN5TDmgDQmTQ2uPSgZthrEyACXBXV/nH jdp/afZAIfNZA9bUGLcmsdP7vSx3SA0VB39C6EIOk+Swp8feCPvbioR6kalMISbq iptzdZg+kUUMdDDnPujdGKbaG1Q/SGb9KxukR4wmN1sqwHiIqNi59vxZJNyN92SH 82ZpQfmy15TDT/IIKdVLVW72z62SIe1qpOwNse9D+JE9iodvVqbddpHYrNvZxxR2 OfxHLqguyVwNBUpomQUAjcSIRnfTkDs0SqaK5vPZ+hY1RnB4GiY= =/T0Y -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT--