From: James Brown via pve-devel <pve-devel@lists.proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "James Brown" <randomvoidmail@foxmail.com>
Subject: Re: [pve-devel] SPAM: [Security] Arbitrary file reading via maliciousVM config
Date: Wed, 27 Nov 2024 08:40:41 +0800 [thread overview]
Message-ID: <mailman.748.1732668076.391.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <mailman.747.1732667455.391.pve-devel@lists.proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 6065 bytes --]
From: "James Brown" <randomvoidmail@foxmail.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] SPAM: [Security] Arbitrary file reading via maliciousVM config
Date: Wed, 27 Nov 2024 08:40:41 +0800
Message-ID: <tencent_34190E94319B774BBF70D0B31FC74F414A0A@qq.com>
This is not a spam.
---Original---
From: "James Brown via pve-devel"<pve-devel@lists.proxmox.com>
Date: Wed, Nov 27, 2024 08:31 AM
To: "Fabio Fantoni via pve-devel"<pve-devel@lists.proxmox.com>;
Cc: "James Brown"<randomvoidmail@foxmail.com>;
Subject: [pve-devel] SPAM: [Security] Arbitrary file reading via maliciousVM config
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-27 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 0:14 [pve-devel] SPAM: [Security] Arbitrary file reading via malicious VM config James Brown via pve-devel
2024-11-27 0:40 ` James Brown via pve-devel [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=mailman.748.1732668076.391.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=randomvoidmail@foxmail.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