From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <tdtemccnp@gmail.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id E351E90EA for <pve-user@lists.proxmox.com>; Fri, 23 Jun 2023 16:28:03 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CB6F7364F6 for <pve-user@lists.proxmox.com>; Fri, 23 Jun 2023 16:28:03 +0200 (CEST) Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-user@lists.proxmox.com>; Fri, 23 Jun 2023 16:28:02 +0200 (CEST) Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-56fff21c2ebso5904887b3.3 for <pve-user@lists.proxmox.com>; Fri, 23 Jun 2023 07:28:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687530474; x=1690122474; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=fvQy38tPNl5dKORbLp4J8YbrRDnOvMlZFlOuA5a1eYc=; b=eH986OG95fJo0N9wYWNZ+AApg8l4jfb9Bowf1IQ4mbH5KuGCyhazMXOAS8trrGFKQb yt1O1MbVUvlSw8UVuI4bCvRryWoR1PoQGDoW2UQPXO7Vr9T5F38ghoJeihUFAa9vLqUU ZWyS7Z7b/N3uueiwSJteYuJxe96Kdu02beP4IAXoHL9QLVaCPxx5n3KMHXzvk1c/29Nd yxQZ48EVuoK+XTio7aYTaiMo6OoTa3pqu2qX8tgoaMmacCjukfNjqVqsm4n8PmYHyVXV 4m+0oZIfg2NODwmmsfh9SZjkscalNuMJXUlX/qxyLFej+dnAyRdxJXKy6sDab2YFAxZK 36KA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687530474; x=1690122474; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=fvQy38tPNl5dKORbLp4J8YbrRDnOvMlZFlOuA5a1eYc=; b=HQFyHFlY8spLvMaP2hgF3kUZEPd5FMgZknrMxOF92igauYKavUXRqvhNLc34LRnja/ YS8io6Cuay2ZtInRvmjavtes/0pIcKPR0hOQgZ/4bjbLu8lJwYJgN5+4E9vkGLEcF7yO 8YYB+j9jtN9YWjwrjNS1rkKaYZ8wR85M7bD3dFTzRchyoC2zd/24PMrkm9T5+trhXWq0 QtLiizaVSfy/ihnCVC+toW2EGDnmMfQuXcNNMcSX6NyR6Youqv4NIgYOpE6ef8L7spT2 YZeFFZ6Peav/B0kWmX3JMh4e+zC+BUCF/ZJ8QXcNodrbXvZQBQw5uk4HHrVl/iVGfL3w L+pw== X-Gm-Message-State: AC+VfDyIhDxM8d7KRYkRFuK299fthlTnv83L+T9pn1zvL1Cd6/IiNgvJ t8mwSg6bdzgVx55Z2qACgPMFtbgRywJpN/oqqbCUT9fx5Gc= X-Google-Smtp-Source: ACHHUZ63GHCu4BsEyr72pMv0QcRN+H/R5cUYne3Jt15OpAXxPv2S64FblOq/t7xs0GBUqP3tbGlkgfEBUSRrLWTcAg4= X-Received: by 2002:a25:e617:0:b0:be4:d7a9:31ff with SMTP id d23-20020a25e617000000b00be4d7a931ffmr17268488ybh.35.1687530474452; Fri, 23 Jun 2023 07:27:54 -0700 (PDT) MIME-Version: 1.0 From: Turritopsis Dohrnii Teo En Ming <tdtemccnp@gmail.com> Date: Fri, 23 Jun 2023 22:27:51 +0800 Message-ID: <CAD3upLsp6QJE7ndv1bQsvJo_aGEAiZyooHrnnY5skgAVraPPWQ@mail.gmail.com> To: pve-user@lists.proxmox.com Cc: ceo@teo-en-ming-corp.com Content-Type: text/plain; charset="UTF-8" X-SPAM-LEVEL: Spam detection results: 0 AWL 0.258 Adjusted score from AWL reputation of From: address BAYES_50 0.8 Bayes spam probability is 40 to 60% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HK_RANDOM_ENVFROM 0.001 Envelope sender username looks random HK_RANDOM_FROM 0.001 From username looks random RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [PVE-User] Is Proxmox VE vulnerable to ransomware like VMware vSphere? X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> List-Post: <mailto:pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 23 Jun 2023 14:28:03 -0000 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.