From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-storage 0/2] fix #7360: esxi: write password file as
Date: Mon, 5 Oct 2026 12:55:21 +0200 [thread overview]
Message-ID: <20261005110306.2197624-1-a.bied-charreton@proxmox.com> (raw)
The first commit fixes the original issue, where at creation time, the
password file would not be saved as UTF-8. This led to decoding errors
when listing VMs (and presumably in the FUSE tool, although I did not
specifically test that path).
The second commit additionally rewrites non-UTF-8-encoded password files
as UTF-8 to catch pre-existing broken password files.
More details in the messages.
Arthur Bied-Charreton (2):
fix #7360: esxi: store password file as utf-8
esxi: rewrite non-UTF-8 password files
src/PVE/Storage/ESXiPlugin.pm | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
--
2.47.3
next reply other threads:[~2026-10-05 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 10:55 Arthur Bied-Charreton [this message]
2026-10-05 10:55 ` [PATCH pve-storage 1/2] fix #7360: esxi: store password file as utf-8 Arthur Bied-Charreton
2026-10-05 10:55 ` [PATCH pve-storage 2/2] esxi: rewrite non-UTF-8 password files Arthur Bied-Charreton
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=20261005110306.2197624-1-a.bied-charreton@proxmox.com \
--to=a.bied-charreton@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.