[-] noobface@lemmy.world 15 points 6 days ago

I'm in this photo and I don't like it.

[-] noobface@lemmy.world 7 points 3 weeks ago

We're seeing connections from IP addresses that aren't even routable on the internet. We're compromised. Time to format.

[-] noobface@lemmy.world 4 points 4 weeks ago

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

[-] noobface@lemmy.world 11 points 1 month ago* (last edited 1 month ago)

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.

[-] noobface@lemmy.world 3 points 2 months ago

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

[-] noobface@lemmy.world 23 points 2 months ago

One of my favorite CS memories was on LAN at quakecon.

1v10. The enemy team just killed 9 of us. I'm the last person up. Demolished them. A couple close moments, but caught almost everyone of them in 1v1s.

After I kill 10 people in a single fucking round, on LAN mind you, some prick on their team types "lucky" in all chat.

I was fucking furious.

So sure enough the very next round my team gets shit on. 1v10 again. I, again, wipe the fucking floor with them. 10 down.

I just stood up and screamed.

[-] noobface@lemmy.world 3 points 3 months ago

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.

[-] noobface@lemmy.world 13 points 4 months ago

Draw a square in √99/π easy steps.

[-] noobface@lemmy.world 5 points 5 months ago

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/

[-] noobface@lemmy.world 10 points 5 months ago

Rebuild time? Yeah it'll take about that long.

view more: next ›

noobface

joined 7 months ago