Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruxtn-008oRp-Ep for pgsql-committers@arkaria.postgresql.org; Thu, 11 Apr 2024 17:07:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ruxtm-00389w-ER for pgsql-committers@arkaria.postgresql.org; Thu, 11 Apr 2024 17:07:42 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruxtm-00389o-3M for pgsql-committers@lists.postgresql.org; Thu, 11 Apr 2024 17:07:42 +0000 Received: from meesny.iki.fi ([2001:67c:2b0:1c1::201]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruxtj-002NRT-1z for pgsql-committers@lists.postgresql.org; Thu, 11 Apr 2024 17:07:40 +0000 Received: from [172.19.157.206] (unknown [212.174.35.38]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: hlinnaka) by meesny.iki.fi (Postfix) with ESMTPSA id 4VFmN36HRqzyT2; Thu, 11 Apr 2024 20:07:31 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1712855254; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PkohNShY8qx0+czECfI7/cDQzLq9Cdzc1/QTRwAqzKA=; b=Px1hDcEedAbYyGeUTLbb6IF4G+2W2hhH0eqdLVPrQPinGIUA9lXaBg8e6EKTR+wA5beuka ssL+T4Fy3BxSJlb6EzWYMWDLxYKrRZ0zY5vEixP16c47sJfFaqN4o5rezfXjTOrufjK1dQ TwjBWUEIC3Y1dkKyt0pWvlM80Q+5xbM= ARC-Seal: i=1; s=meesny; d=iki.fi; t=1712855254; a=rsa-sha256; cv=none; b=GbqO5BDhacyBrBOoq4V6mgHSLviKcPabQUi4gEYFWckQI/g1vwcobE7HMgnwT+i17BcjzR QRTe8FcB2EhNtGkrb4kEWdhwW7Dyh9/oZHtpX3vf3D8dH/PRXslNL/JnjOaE9D7NSXmEcw /Dn44Udd7/UvNg4IVd7np4y5lklzSrc= ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=hlinnaka smtp.mailfrom=hlinnaka@iki.fi ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1712855254; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PkohNShY8qx0+czECfI7/cDQzLq9Cdzc1/QTRwAqzKA=; b=JMVJV3vIRKjuhTyv+3hnieZ1VYS0niC6Lz3NzFInc6n6Cm1BuCu8gmEns70Pt3R9nSNiPv 5UMYYWV5GN0lFO3Vbm+OxJsOE4ptQ0UwcuAjQWaxsaiblARkSkY8s23mRXFboxuq8B2wCD oHqHZOphFSEyiTL7bJwateoUeOIeObo= Message-ID: Date: Thu, 11 Apr 2024 20:07:30 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pgsql: Refactor libpq state machine for negotiating encryption To: Thomas Munro Cc: Heikki Linnakangas , pgsql-committers@lists.postgresql.org, Tom Lane References: <32196.1712791542@sss.pgh.pa.us> Content-Language: en-US From: Heikki Linnakangas In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thanks for the report! On 11/04/2024 02:33, Thomas Munro wrote: > On Thu, Apr 11, 2024 at 11:25 AM Tom Lane wrote: >> Thomas Munro writes: >>> If -Dssl=none and -Dgssapi=disabled, compilation of fe-connect.c >>> fails: call to undeclared function 'encryption_negotiation_failed'. I >>> didn't look too hard, but maybe ENABLE_GSS and USE_GSS are confused? >> >> For me, configure --with-gssapi fails like that, but the other three >> combinations of --with-openssl and --with-gssapi compile OK. I don't >> find it terribly surprising that the buildfarm isn't covering that >> combination ... > > Oops, right, correction to my report: it is indeed -Dssl=none > -Dgssapi=enabled that is broken, not the other combinations. Yes, I misspelled ENABLE_GSS as USE_GSS. After fixing that, the new tests are failing; the expected output for many of the cases is different when GSSAPI support is not compiled in. I think the test tables need to be rearranged some more to take that into account, or we will end up with a ridiculous amount of different expected outputs. I will take a closer look at that tomorrow. As a bandaid fix, we could temporarily disable the new tests with that combination of configure options, it's still better test coverage than not having the tests at all. But given that no buildfarm members are testing that combination I think it can wait a day. -- Heikki Linnakangas Neon (https://neon.tech)