From: Erik Fastermann <e.fastermann@proxmox.com>
To: pbs-devel@lists.proxmox.com
Cc: Erik Fastermann <e.fastermann@proxmox.com>
Subject: [PATCH proxmox-backup 2/5] report: do not include remote passwords
Date: Wed, 9 Sep 2026 13:12:25 +0200 [thread overview]
Message-ID: <20260909111228.217535-3-e.fastermann@proxmox.com> (raw)
In-Reply-To: <20260909111228.217535-1-e.fastermann@proxmox.com>
remote.cfg stores the password or API token of the remote user as a
base64 string, which is trivially reversible. As reports are commonly
shared with third parties, for example in public forum threads, list
the remotes through the API instead, which returns every property but
the password. Proxmox Datacenter Manager handles its own remote
configuration the same way.
The JSON output format is used for two reasons: the text table only
covers a subset of the configured properties, and the report runs all
commands with PROXMOX_OUTPUT_NO_BORDER set, which also suppresses the
table header and thus leaves the columns unlabeled. The latter could
alternatively be solved with a custom text formatter, as done for the
remote listing in Proxmox Datacenter Manager.
Signed-off-by: Erik Fastermann <e.fastermann@proxmox.com>
---
src/server/report.rs | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/server/report.rs b/src/server/report.rs
index d293aa6dd..c22141810 100644
--- a/src/server/report.rs
+++ b/src/server/report.rs
@@ -10,7 +10,6 @@ fn project_files() -> Vec<FileGroup> {
"/etc/proxmox-backup/acl.cfg",
],
),
- ("Remotes", vec!["/etc/proxmox-backup/remote.cfg"]),
(
"Jobs",
vec![
@@ -41,6 +40,10 @@ fn project_commands() -> Vec<StaticArgsCommandSpec> {
("date", vec!["-R"]),
("proxmox-backup-manager", vec!["versions", "--verbose"]),
("proxmox-backup-manager", vec!["subscription", "get"]),
+ (
+ "proxmox-backup-manager",
+ vec!["remote", "list", "--output-format", "json-pretty"],
+ ),
("proxmox-backup-manager", vec!["ldap", "list"]),
("proxmox-backup-manager", vec!["openid", "list"]),
]
--
2.47.3
next prev parent reply other threads:[~2026-09-09 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 11:12 [PATCH proxmox-backup 0/5] report: cover the s3 configuration Erik Fastermann
2026-09-09 11:12 ` [PATCH proxmox-backup 1/5] report: rename mislabeled datastore file group Erik Fastermann
2026-09-09 11:12 ` Erik Fastermann [this message]
2026-09-09 11:12 ` [PATCH proxmox-backup 3/5] report: include the s3 endpoint configuration Erik Fastermann
2026-09-09 11:12 ` [PATCH proxmox-backup 4/5] api: s3: drop unused rpcenv parameter from bucket listing Erik Fastermann
2026-09-09 11:12 ` [PATCH proxmox-backup 5/5] report: list the accessible s3 buckets Erik Fastermann
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=20260909111228.217535-3-e.fastermann@proxmox.com \
--to=e.fastermann@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