From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 3FF041FF0AF for ; Fri, 06 Nov 2026 11:12:45 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id D27E3215AE; Fri, 06 Nov 2026 11:12:41 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 06 Nov 2026 11:12:37 +0100 Message-Id: Subject: Re: [PATCH docs 0/2] update documentation to show that yescrypt is used To: "Shannon Sterz" , X-Mailer: aerc 0.20.0 References: <20261009122729.178682-2-s.sterz@proxmox.com> In-Reply-To: <20261009122729.178682-2-s.sterz@proxmox.com> From: "Shannon Sterz" X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793959957146 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.652 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: N4JAESCMNJJET5YBNQWCPJCPQ5ORPBZK X-Message-ID-Hash: N4JAESCMNJJET5YBNQWCPJCPQ5ORPBZK X-MailFrom: s.sterz@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Superseded: https://lore.proxmox.com/all/179365936285.1979512.1290251679384= 8419942.b4-ty@b4/ and also since applied, so just following up here to avoid confusion. On Fri Oct 9, 2026 at 2:27 PM CEST, Shannon Sterz wrote: > instead of the sha256crypt scheme. also added a note on how to > remediate older accounts potentially still using that scheme. added > that as a second commit so it can optionally be dropped (or squashed > if preferred). > > Shannon Sterz (2): > pveum: document that the pve realm now uses yescrypt > pveum: note that passwords set with old versions may use insecure > hashes > > pveum.adoc | 18 +++++++++++++----- > 1 file changed, 13 insertions(+), 5 deletions(-) > > -- > 2.47.3