From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 7C2EB1FF13B for ; Wed, 06 May 2026 02:09:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4B5CB10E3E; Wed, 6 May 2026 02:09:38 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Hannes Laimer Subject: applied: [PATCH pve-access-control] ldap: decode attribute values as UTF-8 Date: Wed, 6 May 2026 02:08:12 +0200 Message-ID: <177802597087.2857170.7714366665158047246.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260417110451.134766-1-h.laimer@proxmox.com> References: <20260417110451.134766-1-h.laimer@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1778026035906 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: Z35JO3GCG5HU2OMJMGELQDXXZGQCPHJE X-Message-ID-Hash: Z35JO3GCG5HU2OMJMGELQDXXZGQCPHJE X-MailFrom: t.lamprecht@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: On Fri, 17 Apr 2026 13:04:51 +0200, Hannes Laimer wrote: > Net::LDAP's get_value() returns octets as raw bytes as received over > the wire. Per RFC 4511 [0] LDAPString values are UTF-8 encoded, but > Perl does not know that. > > PVE::Tools::encode_text() then re-encodes the bytes as UTF-8, producing > a double-encoded sequence that ends up in user.cfg for any non-ASCII > name. On read decode_text() only undoes one layer, so the GUI and CLI > render the partially-decoded middle form instead of the original text. > > [...] Applied, thanks! [1/1] ldap: decode attribute values as UTF-8 commit: 48197eb464e9e752c794a2618ab4d753634544c9