Search results

I'm a bit skeptical about that claim, not only because it wasn't backed up, but also because it would be incredibly negligent by AMD to not patch this on consumer devices before going public. It would mostly affect ordinary computers though, I don't think a lot of homelabbers visit websites and...

There is a reason this CVE doesn't have a particularly high score. That being said, I am slightly more worried about consumer devices using Zen2 where the potential for supply-chain attacks is larger (think developer notebooks, tech-savvy people that occasionally install random tools from the...

It should be fairly obvious if it does, it prints a bunch of strings straight out of your CPU registers. See the gif from the researchers blog post, it looks something like that. If the output just says "Spawning N Threads...", then prints a line for each CPU Core and stops printing anything...

You could also run the PoC and see if the CPU still "bleeds" # download the PoC, the shady looking URL belongs to the # security researcher who discovered the vuln # (see: https://lock.cmpxchg8b.com/zenbleed.html) wget https://lock.cmpxchg8b.com/files/zenbleed-v5.tar.gz # unpack the tarball...

Can confirm your observation, got the same error when trying to apply the workaround: apt install msr-tools modprobe msr wrmsr -a 0xc0011029 $(($(rdmsr -c 0xc0011029) | (1<<9))) Thanks for the link to the commit, wasn't aware of that one.

I would also be interested about updates regarding that. As per the Security Bulletin from AMD it seems like the microcode update just patches the 2nd Gen AMD EPYC (Rome) CPUs. Consumer-grade CPUs may have to wait until December 2023 to get patched (See same Security Bulletin, "Target Dec...

Thanks for the feedback. I have no experience in SDN whatsoever, so i'm not quite sure on how this works. This would open the possibility to create multiple seperated networks on a single private interface that doesn't support VLANs? Do you have any information on the possible release date of...

After reaching out to the Hetzner Support, they confirmed to me that neither QinQ nor VXLAN is possible on top of the Hetzner vSwitches. Due to the maximum number of 5 vSwitches which can be connected to a dedicated Server and the lack of VLAN Support on the physical private switches, it seems...

Hello there, I am currently struggling to set up QinQ on my Proxmox Cluster. My servers are running on the Hetzner infrastructure and are connected via the Hetzner vSwitch feature. There is a maximum of five vSwitches, which can be connected to a Server, but i want to isolate more than five...

Sorry for the late reply, I guess my diagram wasn't that clear, sorry. 1. All of my three nodes are part of the Proxmox Cluster, but only two of them would run a pfSense firewall. The pfSense on node1 would be the "master" firewall, where pfSense on node2 would be the backup firewall which...

I plan on doing something similar to Iain Stott, but i want to prevent the single point of failure that you also mentioned. I Just did a quick draft on how this problem could potentially be solved for my specific setup. (3 physical servers running a Proxmox Cluster, each having 2 NICs. So that...