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 1tDZw3-001jvz-Q5 for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Nov 2024 01:55:15 +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 1tDZw1-001BjO-6I for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Nov 2024 01:55:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tDZw0-001BjG-PH for pgsql-hackers@lists.postgresql.org; Wed, 20 Nov 2024 01:55:12 +0000 Received: from mail-ua1-x92e.google.com ([2607:f8b0:4864:20::92e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tDZvy-002qTZ-Fu for pgsql-hackers@postgresql.org; Wed, 20 Nov 2024 01:55:12 +0000 Received: by mail-ua1-x92e.google.com with SMTP id a1e0cc1a2514c-85715f21c82so1049865241.3 for ; Tue, 19 Nov 2024 17:55:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732067708; x=1732672508; darn=postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=atkIPxV6GM+hn/X2ioKxzeGUGr9etvYYaNssW9XJPYY=; b=YokNfL2eTZkUPtzZkNvO+RjuAQnVruA9USJx0wAT9YCP6K+ge7qfFZ98fcZIJz6FGf zGn1cJnaE9UNabnhn2As/XWyU1kOEPPutyHTFfg+h/AuXgo2yxaK/tNCk1OUIqtMofGw BtcVcVrJOnn9XL2ARAjsPoeRbvVvlt85D/+J98sQcHGuyQwqD5v3JTPRwT6KgxS8CNBt wqaVXf2CuizMhYvpQ+lgqw3PZIJ5bpjakr07s9axeCrOpNVxzXKqTlUGNWhDN0YR+cPN ma6husa40bWKGt5RSnNR7syHY9bsZEbrKNa6wh2CLmumTFSHvxSMSA8dOGxH/qLcgjHe AaGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732067708; x=1732672508; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=atkIPxV6GM+hn/X2ioKxzeGUGr9etvYYaNssW9XJPYY=; b=oPTJWmTL0+FbXJE2VMT/loRDDmBsOc82Aqeu0pc4aT/Xw8gYp+Nl+xJGZsEf6gsYDc Z7KRSA0y6eHSroRfO7EEUHNcBYaNnU4K84mkxKKl1b8+HY1RESG7LUixZewPRC8jttMn Oo1s6X7NqBC/J+OC4bB7M+CbuZ2og/ZrRhBFRWQDVJow8Xr07dAF+Hdw6Dk50iuNbnmJ yiFTOByuKL07RPAY6+o6vNsfQkFD9kRfNyarV7aUXoBCddgCmdydDNuHVto2T9YxNI5z jV/VK/AaKkR7pKMBkPYOQE6qsQGjncV9xViPdubsy8uiySs0JC3kI1cXxzQnXOB1mHLC i5xg== X-Forwarded-Encrypted: i=1; AJvYcCVjTjlNVZkApOTrAwpPoyapoeqv/4njR6KcDq2cFS+NJ14kTMehTMYRUhT6AEojEeesp4C6dtDGyafrVUjw@postgresql.org X-Gm-Message-State: AOJu0YytTB3+tH+ZDlYBh7AQ2vg0WJpA4goqz+mtochxy+CrsaHRmVjy 6t4nKIoQIYjWfckH2eTiMLgXSFmPMNCQur6UeZXlbPDdqfJHq20o X-Google-Smtp-Source: AGHT+IG+UlfXDAC9HzNSDC+vqb4GNXYXAIgMMc/bSHFz0+57RGj5wEi6EQ9uoRuE2b3xh3TDbQV2Bw== X-Received: by 2002:a05:6102:3a13:b0:4aa:fafa:e100 with SMTP id ada2fe7eead31-4adaf6038d6mr1518541137.26.1732067708209; Tue, 19 Nov 2024 17:55:08 -0800 (PST) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-4646a63cd4asm3498331cf.54.2024.11.19.17.55.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 19 Nov 2024 17:55:07 -0800 (PST) Date: Tue, 19 Nov 2024 19:55:04 -0600 From: Nathan Bossart To: Greg Sabino Mullane Cc: Jim Nasby , Andrew Dunstan , Tom Lane , Heikki Linnakangas , pgsql-hackers Subject: Re: sunsetting md5 password support Message-ID: References: <2735114.1728599306@sss.pgh.pa.us> <17ccc98a-108a-415d-a38c-f12b7baab90d@dunslane.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Nov 19, 2024 at 07:29:27PM -0500, Greg Sabino Mullane wrote: > I just took a fresh look at / compiled this patch, and it all works as > advertised. My one minor nit is this hint: > > HINT: Refer to the PostgreSQL documentation for details about migrating to > another password type. > > We don't really have that in the docs, as near as I can tell, the closest > is 20.5 which says "make all users set new passwords, and change the > authentication method specifications in pg_hba.conf to scram-sha-256." > Maybe that's enough? That was my initial thinking. I think we have a few other options: * Expand the documentation. Perhaps we could add a step-by-step guide for migrating to SCRAM-SHA-256 since more users will need to do so when MD5 password support is removed. * Remove the hint. It's arguably doing little more than pointing out the obvious, and it doesn't actually tell users where in the documentation to look for this information, anyway. * Both of the above. WDYT? -- nathan