Thank you - that explains it, and it corrects my number, which is worth stating plainly for anyone who finds this thread by searching the error string.
I reported ~1 s. It is up to 5 seconds. A single probe measures where it landed inside the...
Adding to a solved thread only because Debian 13 has widened this, and because your third question - "is there a way to manage it globally, without taking care about journald config in each LXC?" - now has a general answer.
Cap the tmpfs itself...
For anyone finding this thread later: this is tracked at Bugzilla #6167 (open, UNDECIDED), where I have added measurements across ten containers.
Two things worth adding here.
First, on Fabian's "you need to do that manually per tmpfs instance"...
If you share details, even which endpoint is affected, people can prepare a patch or other measures.
If you don't, these hackers will keep ransomware machines anyway.
Anyone can put a bait proxmox 7 server on the internet and collect the logs...
Posting this because the existing threads on this are all titled by the cause ("tmpfs wrong size"), and nobody hitting it searches for that. They search the symptoms - and those searches currently return threads about slow storage and HA...
This is both irresponsible and to be expected. Someone should warn then against doing this.
This is helpful (for people running outdated versions).
There have been several SSH vulnerabilities in the (internet) news. People should know better or...
Well, if that makes any difference (I'm not a troll and have been registered for years):
* I had a few bare metal customers with publicly accessible proxmox 7.2 URLs that were hacked;
* Same message as these other users (ramsomware note)
* No...
Sure, but who will put in the time to determine what CVE was used? Then we know for sure which versions are affected. Until then, up to date Proxmox appears to be safe.
To me, it doesn't even make sense we are commenting about Virtualizor and Hetzner on this thread, since the issue is that we may or may not have a security issue within old versions of Proxmox itself, and it isn't even slightly clear yet. Can we...
Der Lizenz-Punkt von @Johannes S ist eigentlich der spannendere, das Codestyle-Argument erledigt sich ja mit genug Nachdruck im Review. Beim DCO unterschreibst du nicht nur "ich steh dafür grade", sondern auch dass du das Recht hast, den Code...
If you share details, even which endpoint is affected, people can prepare a patch or other measures.
If you don't, these hackers will keep ransomware machines anyway.
Anyone can put a bait proxmox 7 server on the internet and collect the logs...
Which version of Proxmox VE are you on? I suspect not a recent one, as the pause and hibernate buttons have been added to the right click menu some time ago.
So if installing Vanilla Debian works, does it stop working when you do this https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie ?
If it starts to fail might be worth raising a bug report with the proxmox team to resolve it if...
Im going to take the weekend to check some of this out and digest it a bit.
So far since the GUI crashes I haven't touched my storage at all and we've been 100% stable which is great though I am at a point where I need to either adjust or create...
Some people in this community are being toxic. This attack was clearly caused by a security vulnerability in PVE, a 0day, yet many are still blaming users for not running the latest version, PVE 9.
However, several points need to be considered...
In any case, I don't think this is a 0day vulnerability, because on this is happen due to out date servers and bad servers administration, to say the least.
Many of this vulnerabilities are well-know documented, such as kernel and ssh...