noobface @ noobface @lemmy.world

🌨️ 💻

---

Read more

Posts

1

Comments

54

Joined

2 yr. ago

there are other kinds of hackers?

yep

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

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

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.

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.

This guy is terminally online with 100+ comments over the last day. Assuming you're arguing with a functioning member of society is misguided. Trolls gonna troll. Don't feed them.

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.

Draw a square in √99/π easy steps.

There are answers, they just take a level of experience to reach that most people aren't cut out for. You gotta be several principal+ IC roles or Dir+ mgr roles in before the patterns congeal into a plan.

Challenge is operating at those levels for extended periods requires a super fucking insane level of competency and dedication. Most people hit that spot and coast till retirement cause you're at $500k+ at FAANG. Few keep looking for new opportunities unless forced to or they're those corporate robot sharks with the dead eyes.

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/

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