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 1kpuNn-0006cd-Pb for pgsql-general@arkaria.postgresql.org; Thu, 17 Dec 2020 14:35:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kpuNl-0005PR-Om for pgsql-general@arkaria.postgresql.org; Thu, 17 Dec 2020 14:35:53 +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 1kpuNl-0005PK-3t for pgsql-general@lists.postgresql.org; Thu, 17 Dec 2020 14:35:53 +0000 Received: from smtpout.smhi.se ([91.192.30.29] helo=smtpout2.smhi.se) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kpuNh-0005ea-Vn for pgsql-general@postgresql.org; Thu, 17 Dec 2020 14:35:52 +0000 Received: from winserv744.ad.smhi.se (winserv744.ad.smhi.se [172.16.6.35]) by smtpout2.smhi.se (Postfix) with ESMTPS id 4734710A7EEB; Thu, 17 Dec 2020 14:35:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smhi.se; s=20180112; t=1608215746; bh=81ShU5O4T6ZHovBT0V0fTzS4QmkYKy81zRH/Tkq/1BE=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=CDT4vKfovZOtYz8EOx8y5IPQx7UNEC11J07x/d5Nr0SMUjku3BI/PL+Vpynw3excd PFaqMKWhwIB6S1ZSD0kgIoo+7mhwMoGjziRA73iK7EHPv+xidV+7V8hz7NHkZBLkKq kKjkkBYdpG3iCpd064bAqBtVVRuIrKgV0VJ2C+L4= Received: from winserv744.ad.smhi.se (172.16.6.35) by winserv744.ad.smhi.se (172.16.6.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 17 Dec 2020 15:35:46 +0100 Received: from winserv744.ad.smhi.se ([fe80::c19c:d0f0:5830:a72b]) by winserv744.ad.smhi.se ([fe80::c19c:d0f0:5830:a72b%9]) with mapi id 15.01.2106.006; Thu, 17 Dec 2020 15:35:46 +0100 From: Gustavsson Mikael To: Tom Lane CC: Kyotaro Horiguchi , "pgsql-general@postgresql.org" , Svensson Peter Subject: SV: SV: Problem with ssl and psql in Postgresql 13 Thread-Topic: SV: Problem with ssl and psql in Postgresql 13 Thread-Index: AQHW1ER+dWnFD/e9/0CWjk1hYinUxan65DcAgAAT2weAAE4KgIAAEwPs Date: Thu, 17 Dec 2020 14:35:45 +0000 Message-ID: References: ,<20201217.172938.170511532557914014.horikyota.ntt@gmail.com> <06191eae74d045e192a786a84a73ba53@smhi.se>,<65644.1608214801@sss.pgh.pa.us> In-Reply-To: <65644.1608214801@sss.pgh.pa.us> Accept-Language: sv-SE, en-US Content-Language: sv-SE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.122.0.145] Content-Type: multipart/alternative; boundary="_000_a748b98ff0a94fe0a1ca54872ec5a25esmhise_" MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --_000_a748b98ff0a94fe0a1ca54872ec5a25esmhise_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, log_connections is on. The ERR message is correct, we do not have an entry = for SSL off. The question is why psql(13) is trying to connect without ssl? 2020-12-17T14:25:09.565566+00:00 server INFO [30-1] pgpid=3D2422778 pguser= =3D[unknown] pghost=3Dnnn.nn.n.nnn pgdb=3D[unknown] pgapp=3D[unknown] LOG: = connection received: host=3Dnnn.nn.n.nnn port=3D40112 2020-12-17T14:25:09.566411+00:00 server ERR [31-1] pgpid=3D2422778 pguser= =3Dkalle pghost=3Dnnn.nn.n.nnn pgdb=3Dpostgres pgapp=3D[unknown] FATAL: no= pg_hba.conf entry for host "nnn.nn.n.nnn", user "kalle", database "postgre= s", SSL off KR Mikael Gustavsson, SMHI ________________________________ Fr=E5n: Tom Lane Skickat: den 17 december 2020 15:20:01 Till: Gustavsson Mikael Kopia: Kyotaro Horiguchi; pgsql-general@postgresql.org; Svensson Peter =C4mne: Re: SV: Problem with ssl and psql in Postgresql 13 Gustavsson Mikael writes: > Clarification, its the same postgresql13 server. I just connect with diff= erent psql-clients. Perhaps turning on log_connections on the server would offer some insight. It sort of looks like the v13 client is trying to connect with SSL, failing for some unknown reason, and falling back to non-SSL which also fails. regards, tom lane --_000_a748b98ff0a94fe0a1ca54872ec5a25esmhise_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable


Hi,

log_connections is on. The ERR message is correct, we do not have an e= ntry for SSL off. 
The question is why psql(13) is trying to connect without ssl?

2020-12-17T14:25:09.565566+00:00 server INFO [30-1] pgpid=3D242277= 8 pguser=3D[unknown] pghost=3Dnnn.nn.n.nnn pgdb=3D[unknown] pgapp=3D[unknow= n] LOG:  connection received: host=3Dnnn.nn.n.nnn port=3D40112
2020-12-17T14:25:09.566411+00:00 server ERR [31-1] pgpid=3D2422778= pguser=3Dkalle pghost=3Dnnn.nn.n.nnn pgdb=3Dpostgres pgapp=3D[unknown] FAT= AL:  no pg_hba.conf entry for host "nnn.nn.n.nnn", user &quo= t;kalle", database "postgres", SSL off

KR
Mikael Gustavsson, SMHI

Fr=E5n: Tom Lane <tgl@= sss.pgh.pa.us>
Skickat: den 17 december 2020 15:20:01
Till: Gustavsson Mikael
Kopia: Kyotaro Horiguchi; pgsql-general@postgresql.org; Svensson Pet= er
=C4mne: Re: SV: Problem with ssl and psql in Postgresql 13
 
Gustavsson Mikael <mikael.gustavsson@smhi.se>= ; writes:
> Clarification, its the same postgresql13 server. I just connect with d= ifferent psql-clients.

Perhaps turning on log_connections on the server would offer some
insight.  It sort of looks like the v13 client is trying to connect with SSL, failing for some unknown reason, and falling back to non-SSL
which also fails.

            &nb= sp;           regards, to= m lane


 --_000_a748b98ff0a94fe0a1ca54872ec5a25esmhise_--