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 1ru3oz-0025a7-L5 for pgsql-committers@arkaria.postgresql.org; Tue, 09 Apr 2024 05:15:02 +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 1ru3oy-00HVs9-P8 for pgsql-committers@arkaria.postgresql.org; Tue, 09 Apr 2024 05:15:00 +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 1ru3oy-00HVs1-ID for pgsql-committers@lists.postgresql.org; Tue, 09 Apr 2024 05:15:00 +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 1ru3ov-001wcg-Q8 for pgsql-committers@lists.postgresql.org; Tue, 09 Apr 2024 05:14:59 +0000 Received: from [192.168.1.115] (dsl-hkibng22-54f8db-125.dhcp.inet.fi [84.248.219.125]) (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 4VDDfk1YD6zyS6; Tue, 9 Apr 2024 08:14:54 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1712639694; 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=DppA32f7YMm58jQ09wi3LBTi/k64OywLMm6D8l4l5xM=; b=j1dmuO2j9Lpgwi8u644zmCOyY8DL6PJFTqsrnCuBMXdPoBfbH9Iw/FsKsK8jM2FSKRxr0b zLIP+MmmsMeOXPp5qElpuVqp06YhDi5Qyo7SYXlEOWunzqegiG3xYHr8rbuhDSjSp5pKan EKUN63Tjmd4h9MYLF/JZNs7zEjehK+w= ARC-Seal: i=1; s=meesny; d=iki.fi; t=1712639694; a=rsa-sha256; cv=none; b=DKivbSAvSu5ql21wA+4IffSO0RQdaiuRwfHlRlizgGqCIXLXpMVzDwmhfBuPPh/pOK8wIw 8N6AE/36JjoKLqC7i6X3+Lwj8yvn1ghnGqryat1Fx41kEaPK6u2ifWrkqtY9Rv+c4amO6k s13BCDUvdTXfSYiYDZ62vRpA+LwSCJE= 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=1712639694; 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=DppA32f7YMm58jQ09wi3LBTi/k64OywLMm6D8l4l5xM=; b=R/PkaBdMAeHUMl395f7c1FBVRXwYdbt9hc0tiqKfhhyUz2UdqiZDWTWnpNR5RWGXCJcPSz QcrL8G8PKZkNmsz3bw5EPER4nqFdpjPmq/leKVW5z2kU7ow8LjN4w34gSGjObMBL5TaGM/ 3093qOc3g38XmvD8LLrP0CRh7YHHssY= Message-ID: <7c8d2655-9d2d-42e9-94c1-cee76e08468b@iki.fi> Date: Tue, 9 Apr 2024 08:14:53 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pgsql: With gssencmode='require', check credential cache before connect Content-Language: en-US To: Kyotaro Horiguchi Cc: pgsql-committers@lists.postgresql.org References: <20240409.104613.1653854506705708036.horikyota.ntt@gmail.com> From: Heikki Linnakangas In-Reply-To: <20240409.104613.1653854506705708036.horikyota.ntt@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 09/04/2024 04:46, Kyotaro Horiguchi wrote: > Hello. > > At Sun, 07 Apr 2024 23:50:08 +0000, Heikki Linnakangas wrote in >> With gssencmode='require', check credential cache before connecting > > This commit adds the following error message (indentations are adjusted): > > + libpq_append_conn_error(conn, > + "GSSAPI encryption required but it is not supported over a local socket)"); > > The closing parenthesis at the end of the message seems to be a > leftover from editing. Fixed, thanks! > About the following message: > > + libpq_append_conn_error(conn, "could not set ssl alpn extension: %s", err); > > I'm not sure about the policy for writing acronyms in lowercase, but > other occurrences of ALPN (in backend code) seem to be written in > uppercase. Changed to uppercase. I also changed "ssl" to uppercase, for consistency with the "could not set SSL Server Name Indication (SNI)" message earlier. To be even more consistent, we should perhaps spell out "SSL Application-Layer Protocol Negotiation (ALPN)", but that's pretty long and I don't think it really helps the user. It really should not fail, and there isn't anything the user can really do if that fails. Anyone who doesn't already know what ALPN is will need to google it anyway. -- Heikki Linnakangas Neon (https://neon.tech)