From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Hannes Laimer <h.laimer@proxmox.com>
Subject: applied: [PATCH pve-access-control] ldap: decode attribute values as UTF-8
Date: Wed, 6 May 2026 02:08:12 +0200 [thread overview]
Message-ID: <177802597087.2857170.7714366665158047246.b4-ty@b4> (raw)
In-Reply-To: <20260417110451.134766-1-h.laimer@proxmox.com>
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
prev parent reply other threads:[~2026-05-06 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 11:04 [PATCH pve-access-control] ldap: decode attribute values as UTF-8 Hannes Laimer
2026-05-06 0:08 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177802597087.2857170.7714366665158047246.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.