From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH proxmox 1/1] ini: remove debug statement
Date: Thu, 2 Apr 2026 10:10:18 +0200 [thread overview]
Message-ID: <20260402081021.75059-1-s.hanreich@proxmox.com> (raw)
Seems leftover from development and potentially prints sensitive
content (e.g. private keys in wireguard config).
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
proxmox-ini/src/lib.rs | 2 --
1 file changed, 2 deletions(-)
diff --git a/proxmox-ini/src/lib.rs b/proxmox-ini/src/lib.rs
index 921a92e8..f4162bb0 100644
--- a/proxmox-ini/src/lib.rs
+++ b/proxmox-ini/src/lib.rs
@@ -338,8 +338,6 @@ impl<'a> ser::SerializeMap for IniMapSerializer<'a> {
self.ser.buf += &serializer.buf;
}
SerializedType::Section => {
- dbg!(&serializer.buf, &serializer.sections);
-
if !serializer.buf.is_empty() {
// First, add all top-level entries from the map into a new section,
// in case we serialized a map
--
2.47.3
next reply other threads:[~2026-04-02 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 8:10 Stefan Hanreich [this message]
2026-04-02 12:59 ` Wolfgang Bumiller
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=20260402081021.75059-1-s.hanreich@proxmox.com \
--to=s.hanreich@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