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 1jc73O-0002ma-OL for pgsql-hackers@arkaria.postgresql.org; Fri, 22 May 2020 12:45:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jc73N-0007rU-LI for pgsql-hackers@arkaria.postgresql.org; Fri, 22 May 2020 12:45:33 +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 1jc73N-0007rM-Dl for pgsql-hackers@lists.postgresql.org; Fri, 22 May 2020 12:45:33 +0000 Received: from wforward3-smtp.messagingengine.com ([64.147.123.22]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jc73D-0003EZ-1N for pgsql-hackers@postgresql.org; Fri, 22 May 2020 12:45:32 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.west.internal (Postfix) with ESMTP id A1160E23 for ; Fri, 22 May 2020 08:45:21 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 22 May 2020 08:45:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=kAr9py TtJnmOfEoVZ4cDvjCCRe6VklZA1IZsS5xI0+M=; b=h2J4fV1Qkfc8CZMaDwT1Uh EmJmKMcvR6lksbxasQCG61s2R7eqJ5Xk6DmxDYLss8l4irb0xe0S9rV06rA/pS97 +5/MCgDb1DgWEJXwoAd+ZtoirDqXyBMQOGj9HFGyu3iJMzz1AnKYKd39PjZvK2xh xOKClsQtTISQJqHRhFCIzHpjr7i1iVNy7lmjc50i6Y2BCxcz1unyhgRDCS0eXHR9 s6F1t5CaAQoI53bYEtk2M7Lj0KK8d6jqzhYM4zzNEk/seZ6K+vKf77ZmkOTu3W7E WltX1ljk3FDhS051lDymGE41MsZ7WBr2EipqsUW2T6dsxpNCsyQOyhK4RRmDr6Hg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddufedgheehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefvhffuohfkffgfgggtgfesthejre dttdefjeenucfhrhhomheprfgvthgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdr vghishgvnhhtrhgruhhtsedvnhguqhhurggurhgrnhhtrdgtohhmqeenucggtffrrghtth gvrhhnpeetfedvgfejueeivefgffegjeettdehudeikeevffeludegtdegieegffelvefg vdenucffohhmrghinhepvdhnughquhgrughrrghnthdrtghomhenucfkphepleefrddvge efrdekvddrvdegieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnughquhgrughrrghnthdrtg homh X-ME-Proxy: Received: from april.pezone.net (p5df352f6.dip0.t-ipconnect.de [93.243.82.246]) by mail.messagingengine.com (Postfix) with ESMTPA id AFCED328005A for ; Fri, 22 May 2020 08:45:20 -0400 (EDT) To: pgsql-hackers From: Peter Eisentraut Subject: password_encryption default Organization: 2ndQuadrant Message-ID: Date: Fri, 22 May 2020 14:45:19 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk We didn't get anywhere with making the default authentication method in a source build anything other than trust. But perhaps we should change the default for password_encryption to nudge people to adopt SCRAM? Right now, passwords are still hashed using MD5 by default, unless you specify scram-sha-256 using initdb -A or similar. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services