From 12:48 of the video:
Gamers Nexus: “Were you able to lock in contracts for memory with the suppliers directly or did you have to jump through a bunch of hoops or…”
Rep from Valve: “Look there’s no contract, there’s nothing. Those guys…they are…they give us a price every month, and they say ‘you can buy that many’, and it’s yes or no, and if we say no then they never talk to us again”.
Gamers Nexus also links another video they made specifically about the DRAM cartel.
fruit videos? is there a recent trend I missed?
You can pursue both…
I remember reading that the only way a restaurant can pay less than minimum wage is if the employees make enough tip to make up for it. In other words if everybody just stopped tipping, it would force restaurants to pay normal wage right?
If I have a bare metal dedicated server, which has only access to IPs contained in my whitelist on a dedicated opnsense, I have less to wory about.
Sure, someone could still find a openbsd/opnsense exploit and get me, but my point is: complex systems break in complex ways, the more complex systems you use, the more attack surface u have, need to know and understand to control and mitigate it.
The way I would frame it is: using complex systems that you are unfamiliar with is risky. In your case, you are familiar with OPNsense and firewalls. So that may be the more secure option for you. But for somebody who isn’t familiar with firewalls, there are a lot of ways to mess up. For example, IP and mac spoofing is very easy. OPNsense and firewalls often don’t have very good defense against IP spoofing, especially if the malware is already inside your LAN (for example, a malicious app running on a smartphone).
Using proxmox and other virtualization platforms has one big advantage: you can experiment and play around and learn, without much risk. With a physical server, if you mess up and get infected, you may have to throw away the whole server. You can’t just re-install the OS, because the malware could have installed a rootkit or infected the bios or other firmware. But with a VM, if the VM gets infected you can just delete the VM and create a new one. One of the main goals of a hypervisor is to sandbox the VM, so that malware is contained.
“best” is of course subjective. Bare metal could be better, but imo the marginally smaller attack surface isn’t worth it. If the Qubes project trusts that a hypervisor is secure enough, then I trust it as well.
I run 10+ VMs all the time, no way am I going to buy 10 bare metal servers. The ability to create new secure environments on-demand is unbeatable.
And bare metal does have security disadvantages too. It has a physical attack surface that a VM does not. For example, defending against usb attacks. Of course for a VM, the hypervisor/host can be attacked physically, but you only need to worry about securing that one. Securing 10 physical servers is a lot more work than securing just one, so you’re more likely to get lazy, slip up, etc.
I remember Linus Tech Tips had a hot take once that adblocking/bypassing was the same as piracy. I agree with him.
On Youtube, the user is expected to watch ads to get the video. That’s the cost of the service, how it was designed. Using circumventions to get the content without paying the price, is piracy.
And personally I’m all for piracy.
Rustdesk did have some massive controversies in the past, like:
Which raises doubts as to how trustworthy the development team is.
And while some other people say “it’s ok that was in the past they fixed it”, keep in mind that most of Brave Browser’s controversies were in the past, and yet lemmy still hasn’t forgiven them yet…so I’d like to know how long it takes for lemmy to forgive past mistakes
Nobody believes virtualization is perfect, it’s just the best we got because:
And anyways, even a separate physical computer can be hacked. If it has networking, there could be a vulnerability in the networking stack. Just making an outbound tcp connection can be enough to be pwned.
I think the closest thing we have to an “invincible” system is seL4, but I rarely hear about amybody using them
copy fail allows VMs to infect the host system? I thought it was a kernel vulnerability, not a hypervisor vulnerability. Containers and LXCs share the kernel with the host, full VMs do not. So a kernel exploit allows container escape but not VM escape.
Kernel exploits happen a few times a year. Hypervisor exploits and VM escapes are VERY rare.
Using SSH for clustering is optional. You can just use normal VMs. You don’t have to install SSH into the VM, you can view it through proxmox. The only difference between a VM and a separate physical machine is the hypervisor, so the only security difference is the security of the hypervisor. And as I mentioned, hypervisor exploits are very rare.
Edit: for a sense of perspective, think about this. Almost every major tech company in the world relies on hypervisors for security. Qubes OS, known in the privacy/security world as one of if not the most secure OSes, relies on the hypervisor for security. An easily exploitable hypervisor escape would be a vulnerability on the scale of the XZ utils backdoor (which was unsuccessful). I have not seen a vulnerability of that scale since heartbleed.
Edit2: a word
I recommend proxmox. One VM for sensitive private data and backups, one VM for stuff exposed to the internet
Linux does this too. GNOME and KDE both do web searches from the search menu by default (to be more precise they search the app store, which is on the web)