Comments like this is why I come to Red…Lemmy.

Imagine never hearing the word “No.” as a complete sentence ever again in your life.

But how will they know what movies to watch or what’s the latest in fashion?

Hey Ralph can you get that post-it from the bottom of your keyboard?

yep

I dunno I RMA’d my Nomad so many times.

Industrial espionage

If budget is no object it’s only kind of a pain in the ass with Nvidia’s vGPU solutions for data centers. Even with $10 grand spent there’s hypervisor compatibility issues, license servers, compatibility challenges with drivers for games/consumer OS’s on hypervisors, and other inane garbage.

Consumer wise it’s technically the easiest it’s ever been with SRIOV support for hardware accelerating VMs on Intel 13 & 14 gen procs with iGPUs, however iGPU performance is kinda dogshit, drivers are wonky, and multiple display heads being passed through to VMs is weird for hypervisors.

On the docker side of things YMMV based on what you’re trying to accomplish. Technically nvidia container toolkit does support CUDA & display heads for containers: https://hub.docker.com/r/nvidia/vulkan/tags. I haven’t gotten it working yet, but this is the basis for my next set of experiments.

Are you running redundant routers, connections, ISPs…etc? Compromise is part of the design process. If you have resiliency requirements redundancy will help, but it ratchets up complexity and cost.

Security has the same kinds of compromises. I prefer to build security from the network up, leveraging tools like VLANs to start building the moat. Realistically, your reverse proxy is likely battle tested if it’s configured correctly and updated. It’ll probably be the most secure component in your stack. If that’s configured correctly and gets popped, half the Internet is already a wasteland.

If you’re running containers, yeah technically there are escape vectors, but again your attacker would need to pop the proxy software. It’d probably be way easier to go after the apps themselves.

Do something like this with NICs on each subnet:

DMZ VLAN <-> Proxy <-> Services VLAN

Double NIC on the proxy. One in each VLAN.

Easy to fix moving forward, but a really public admission of “oops” to all current phone key users who will have to reauth their phones.

The idea is to squeeze as much revenue from the largest 600 clients while they desperately attempt to move to a different virtualization platform: https://www.theregister.com/2022/05/30/broadcom_strategy_vmware_customer_impact/