• 1 Post
  • 81 Comments
Joined 2 years ago
cake
Cake day: October 28th, 2024

help-circle
  • 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 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.













  • What kind of abuse are you talking about? I doubt you’re talking about a 51% attack, which is incredibly hard. I’m guessing you are talking about social engineering, like where some scammer gets a poor soul to leak their bitcoin wallet or something like that.

    In these cases, yes a centralized payment system can be useful, because the authority in charge can just reverse transactions that are deemed fraudulent or the result of a scam. But that same authority can do things like ban all payments to Steam for porn games (like the recent Visa Mastercard drama). That same authority can say “GrapheneOS and Pinephone users aren’t allowed to make NFC payments”.

    In cases like these it would be nice for there to be an alternative to centralized systems, at least for those technologically literate enough to use these alternative systems.



  • What a lot of people are forgetting to mention here, is that the reason why maintaining a browser is so hard is because Google keeps updating the standards, and has the resources to do so, while Firefox struggles to keep up.

    Remember, Google Chrome is Google’s OS. Like Microsoft has Windows, and Apple has MacOS. This is why web standards include support for USB, GPU, and other esoteric use cases. It’s in Google’s best interest for users to use web apps to do things instead of desktop apps, since that means they are likely using Chrome, within Google’s control. And Google has a perverse incentive to keep evolving these standards so that other browsers struggle to keep up, and their browsers feel outdated and feature lacking relative to Chrome.





  • Even if you have a password for your ssh key, malware on your system can just wait until you enter the password.

    My point is that SSH access is very powerful, and effectively means that the security of the SSH server is reduced to the security of the SSH client. If your SSH client is pwned, so is your server. If you have 10 devices each with ssh access to each other, then if any one device is pwned, all devices are pwned as well.

    This is not the case for systems designed for file sharing only. For example with syncthing, if one device gets pwned, all it can do is send files to the other devices.