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 1kiJc1-0000SQ-UQ for pgsql-bugs@arkaria.postgresql.org; Thu, 26 Nov 2020 15:55:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kiJbz-0004pr-Ho for pgsql-bugs@arkaria.postgresql.org; Thu, 26 Nov 2020 15:55:11 +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 1kiJbz-0004pM-CN for pgsql-bugs@lists.postgresql.org; Thu, 26 Nov 2020 15:55:11 +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 1kiJbw-0006Wu-AP for pgsql-bugs@lists.postgresql.org; Thu, 26 Nov 2020 15:55:11 +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 0AQFsxPO619349; Thu, 26 Nov 2020 10:54:59 -0500 From: Tom Lane To: Walter Weinmann cc: walter@konnexions.ch, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16736: SCRAM authentication is not supported by this driver In-reply-to: References: <16736-08a2d0d16b76e87e@postgresql.org> <1546115.1605980695@sss.pgh.pa.us> Comments: In-reply-to Walter Weinmann message dated "Thu, 26 Nov 2020 09:21:09 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <619347.1606406099.1@sss.pgh.pa.us> Date: Thu, 26 Nov 2020 10:54:59 -0500 Message-ID: <619348.1606406099@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Walter Weinmann writes: > I use the official PostgreSQL image of DockerHub (docker pull > postgres:13.1) Is it possible that in 13.1 the default password encryption > has been changed to scram-sha-256? That would explain my problem, because > in the image the parameter *password_encryption* in *postgresql.conf* is > commented out. Seems unlikely, but the pg_settings row for password_encryption would tell you more about what the active setting is and where it came from. regards, tom lane