From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, security@proxmox.com,
s.sterz@proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: applied: [PATCH container v2 0/3] forbid newlines in OCI config-items and raw lxc config
Date: Fri, 28 Aug 2026 19:42:32 +0200 [thread overview]
Message-ID: <178793894903.3309998.590875316055191260.b4-ty@b4> (raw)
In-Reply-To: <20260827160858.623104-1-s.ivanov@proxmox.com>
On Thu, 27 Aug 2026 18:08:35 +0200, Stoiko Ivanov wrote:
> v1->v2:
> * add additional patch that reject \r in addition to \n (symmetric to what
> we do while parsing) - minimally tested by installing it on my host and
> restarting my running containers
>
> original cover-letter for v1:
>
> [...]
Applied, thanks!
[1/3] config: only skip tab as control char for oci images
commit: 9658a90fd0daf69895c614ac88f565328d0aa932
[2/3] config: check for newlines in low level lxc config options
commit: 1ed076bd65d1cd9970cf656115069e9be9547b99
[3/3] config: reject \r in addition to \n inside config value
commit: ad7d8a0942886cac7e91918ad7d9a765385c08be
parent reply other threads:[~2026-08-28 17:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260827160858.623104-1-s.ivanov@proxmox.com>]
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=178793894903.3309998.590875316055191260.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
--cc=s.sterz@proxmox.com \
--cc=security@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