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 1jbQFv-0007fa-G4 for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 20 May 2020 15:03:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jbQFu-00054O-8t for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 20 May 2020 15:03:38 +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 1jbQFu-00054H-35 for pgsql-pkg-yum@lists.postgresql.org; Wed, 20 May 2020 15:03:38 +0000 Received: from forward5-smtp.messagingengine.com ([66.111.4.239]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbQFr-0004Iw-Nx for pgsql-pkg-yum@postgresql.org; Wed, 20 May 2020 15:03:36 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.nyi.internal (Postfix) with ESMTP id CD74519406D2; Wed, 20 May 2020 11:03:34 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 20 May 2020 11:03:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=zxVjCQGASv3YiOx3e3kymig5GlCQntPV9gxoQHWCS sM=; b=JMUcoVSCYNST1n/nyTZQxv3ufJ6H8W0a1Rzg4b0YYmUqjlSyaWWcyndBV FlV9sJGpb+gnFzSCfeUQLS44A6afCiZ623j4TsARAdnsDmMiY22f53mv2sfWqrEi OJgpdxX72MKUZYz1b2m35S3WO5rT4l29c/EV7HSuBZn3Ic/b59/Q8pD4ZxFVsxbK l9R9KhpfeTqQjvaHtNOipX4HgCDnOQ81gtSHd/oXPC1e3QUw7oeWKSL9iaazLnj6 4uGqoGqFavowIGRKdQR2jPeORfphs2y624sgDJ/YkbFpuxlVQaqBDKnZNPE5hW4f /vnxI6QX5YZQAhIBD5DMzXk77HLTg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddtledgkedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeehnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuggftrfgrthhtvghrnhepveeuteelvdeuudfggfev udegudfhvdekgeeufefhtdeguedugefhheeugeefhfeinecuffhomhgrihhnpedvnhguqh hurggurhgrnhhtrdgtohhmnecukfhppeelfedrvdegfedrkedvrddvgeeinecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghish gvnhhtrhgruhhtsedvnhguqhhurggurhgrnhhtrdgtohhm 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 D518E3280060; Wed, 20 May 2020 11:03:32 -0400 (EDT) Subject: Re: Can we stop defaulting to 'ident'? To: Stephen Frost References: <7761d006b5ace13a4d86ce489123e5004aaf8b6c.camel@gunduz.org> <20200519212710.GQ13712@tamriel.snowman.net> <6089d4c8e262dd6fe8a6510c283e674543a24b5c.camel@gunduz.org> <3869d8c9-c212-8d73-52f4-13b03abe4813@2ndquadrant.com> <20200520134035.GD296739@msg.df7cb.de> <3a7d55ed-6abb-2005-23d7-8411bb9f5651@2ndquadrant.com> <20200520145752.GD3418@tamriel.snowman.net> Cc: Christoph Berg , =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= , Craig Ringer , pgsql-pkg-yum From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <32b7fe66-f0e6-42e5-3c95-7d123e7d7f6d@2ndquadrant.com> Date: Wed, 20 May 2020 17:03:32 +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 In-Reply-To: <20200520145752.GD3418@tamriel.snowman.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-05-20 16:57, Stephen Frost wrote: > Greetings, > > * Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote: >> Sorry, I should have been more clear. The upstream default of the GUC >> parameter "password_encryption" is md5. > > Which, really, is pretty broken when we're going to be having our > packagers setting up pg_hba.conf to use scram- at the *very* least it's > ridiculously misleading because we're going to have SCRAM in pg_hba.conf > but passwords actually stored as md5 and therefore we won't be getting > the benefits from SCRAM auth (though it should still work, of course, > since the SCRAM mode will fall back to working with an md5 password). Devrim's commit to pgrpms did include a change to the default setting of password_encryption, so it appears to be correct as far as it goes. But this leads to other questions, like, what should pg_upgrade do? These discussions should be had, but perhaps not on the RPM packaging list the night before the release. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services