public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH-SERIES qemu-server/storage/common v2 0/4] fix UTF-8 handling for PBS_PASSWORD
Date: Mon, 09 Mar 2026 14:45:56 +0100	[thread overview]
Message-ID: <s8oa4whw1yj.fsf@toolbox> (raw)
In-Reply-To: <20260309130653.90674-1-f.ebner@proxmox.com> (Fiona Ebner's message of "Mon, 9 Mar 2026 14:06:39 +0100")

Fiona Ebner <f.ebner@proxmox.com> writes:

> Changes in v2:
> * Improve commit message - the ENV issues only happen when Perl's
>   internal representation is not valid UTF-8 itself.
> * Rebase on latest master.
>
> There are multiple issues with UTF-8 password handling for PBS backup:
>
> 1. As reported in the community forum, PBS backup of VMs would not
> work when the password contained a multi-byte UTF-8 character. The
> first patch fixes this by properly encoding the JSON sent via QMP.
>
> 2. The PBS password is saved as UTF-8 and decoded to Perl's internal
> string representation upon reading from the password file. When the
> password is not valid UTF-8 in Perl's internal representation, which
> for example happens with a password like 'ääääöööö', backing up a
> diskless VM would fail with:
>> Error: error building client for repository XXX -
>> PBS_PASSWORD contains bad characters
>
> 3. The same error would occur for uploading the log file after backup, as
> well as extracting the configuration file from backup.
>
> 4. Restoring would fail with:
>> restore failed: invalid utf-8 sequence of 1 bytes from index 0
>
> Fix issues 2.-4. by properly encoding the value for the PBS_PASSWORD
> environment variable value again as UTF-8.
>
> 5. For PMG, using passwords that would be auto-encoded by Perl as either
> ASCII or UTF-8 already worked, but other encodings would not, for
> example ISO-8859 would result in:
>> proxmox-backup-client failed: Error: error building client for
>> repository latin@pbs@10.10.100.180:8007:bigone - PBS_PASSWORD
>> contains bad characters (500)
>
> Follow pve-storage commit 5245e04 ("fix #5181: pbs: store and read
> passwords as unicode") and align the behavior of the storage plugin
> and pbs client module.
>

I tested:

- Created a user on a pbs with bär as its password
- On a pve create a pbs storage for this user via pvesm add
- Check outs its `pvesm status`
- Created backups of a VM while if both offline and online
- The same but without any attached disk

It works as expected.

Tested-by: Maximiliano Sandoval <m.sandoval@proxmox.com>

-- 
Maximiliano




      parent reply	other threads:[~2026-03-09 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 13:06 Fiona Ebner
2026-03-09 13:06 ` [PATCH qemu-server v2 1/4] qmp client: encode JSON as UTF-8 to fix PBS backup when password contains multi-byte UTF-8 Fiona Ebner
2026-03-09 13:06 ` [PATCH qemu-server v2 2/4] pbs: properly encode PBS password as UTF-8 when setting the environment variable Fiona Ebner
2026-03-09 13:06 ` [PATCH storage v2 3/4] pbs plugin: raw client command: " Fiona Ebner
2026-03-09 13:06 ` [PATCH common v2 4/4] pbs client: allow using password that would be auto-encoded as neither ASCII nor UTF-8 Fiona Ebner
2026-03-09 13:45 ` Maximiliano Sandoval [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=s8oa4whw1yj.fsf@toolbox \
    --to=m.sandoval@proxmox.com \
    --cc=f.ebner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal