From: Christian Ebner <c.ebner@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@proxmox.com>,
pbs-devel@lists.proxmox.com
Subject: Re: [PATCH backup v4 0/4] fix #7054: client: remove trailing newlines from credentials
Date: Wed, 22 Jul 2026 14:01:35 +0200 [thread overview]
Message-ID: <f935223a-e7c7-4921-b65e-5e96acc24a4b@proxmox.com> (raw)
In-Reply-To: <20260706080246.108256-1-m.sandoval@proxmox.com>
On 7/6/26 10:03 AM, Maximiliano Sandoval wrote:
> See the first commit for more details.
>
> This was tested with proxmox-backup-client making a login/backup using different
> credentials with and without newlines. The commands were similar to the
> systemd-run commands at the Backup Client Usage docs.
>
> I did not find a way to create the keyfile with newlines in its password using
> proxmox-backup-client since it reads from the tty stdin, but surely it could be
> created manually. Perhaps it is safe-ish to also remove trailing control
> characters from the encryption password but this seems a safer approach for now.
>
> Differences from v3:
> - Move trim_end calls to get_password, get_repository, get_fingerprint
> - Remove "in general" from the documentation
> - Rename get_secret_impl to get_secret_string
>
> Diferences from v2:
> - Reworded commit messages following feedback form v1.
>
> Diferences from v1:
> - Always do an extra allocation to keep the code clean
> - Rename password to blob
> - Only strip newlines on passwords
>
Thanks for the new version of the patches, code is cleaner now IMO.
Tested newlines and/or whitespaces are stripped as expected by adapting
the respective systemd credentials files.
Consider:
Reviewed-by: Christian Ebner <c.ebner@proxmox.com>
Tested-by: Christian Ebner <c.ebner@proxmox.com>
prev parent reply other threads:[~2026-07-22 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 8:02 [PATCH backup v4 0/4] fix #7054: client: remove trailing newlines from credentials Maximiliano Sandoval
2026-07-06 8:02 ` [PATCH backup v4 1/4] " Maximiliano Sandoval
2026-07-06 8:02 ` [PATCH backup v4 2/4] docs: client: document further password constrains Maximiliano Sandoval
2026-07-06 8:02 ` [PATCH backup v4 3/4] client: rename password to blob Maximiliano Sandoval
2026-07-06 8:02 ` [PATCH backup v4 4/4] client: Rename get_secret_impl method Maximiliano Sandoval
2026-07-22 12:01 ` Christian Ebner [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=f935223a-e7c7-4921-b65e-5e96acc24a4b@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=m.sandoval@proxmox.com \
--cc=pbs-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