From: Turritopsis Dohrnii Teo En Ming <tdtemccnp@gmail.com>
To: pve-user@lists.proxmox.com
Cc: ceo@teo-en-ming-corp.com
Subject: [PVE-User] Is Proxmox VE vulnerable to ransomware like VMware vSphere?
Date: Fri, 23 Jun 2023 22:27:51 +0800 [thread overview]
Message-ID: <CAD3upLsp6QJE7ndv1bQsvJo_aGEAiZyooHrnnY5skgAVraPPWQ@mail.gmail.com> (raw)
Subject: Is Proxmox VE vulnerable to ransomware like VMware vSphere?
Good day from Singapore,
Recently, VMware vSphere has come under the spotlight because tens of
thousands of VMware vSphere installations are vulnerable to
ransomware. Ransomware gangs are actively targeting VMware vSphere. Is
Proxmox VE vulnerable to ransomware like VMware vSphere?
Please advise. Thank you.
Regards,
Mr. Turritopsis Dohrnii Teo En Ming
Targeted Individual in Singapore
Blogs:
https://tdtemcerts.blogspot.com
https://tdtemcerts.wordpress.com
GIMP also stands for Government-Induced Medical Problems.
next reply other threads:[~2023-06-23 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 14:27 Turritopsis Dohrnii Teo En Ming [this message]
2023-06-23 16:57 ` Stefan
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=CAD3upLsp6QJE7ndv1bQsvJo_aGEAiZyooHrnnY5skgAVraPPWQ@mail.gmail.com \
--to=tdtemccnp@gmail.com \
--cc=ceo@teo-en-ming-corp.com \
--cc=pve-user@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