• 1 Post
  • 88 Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle








  • Hah yeah, I’ve definitely pulled the plug on my router before because I wasn’t sure what I was seeing.

    I mean, cybersecurity I would consider to be a research field. In practice, yeah, it’s a bunch of people just doing their best.

    I tend to keep everything inside my network and only expose what I need visible on non standard ports, one of those being a VPN. It’s not that I couldn’t run these services public facing, it’s that the people taking the time to constantly update, configure, and auditing everything full time to head off red team are being paid. I don’t need to deal with an attack surface any larger than it needs to be, ain’t nobody got time for that.


  • The ability to generate a bunch of traffic that looks like it’s coming from legit, every-day residential IPs is invaluable to disinformation campaigns. If they can get persistence in your network, they can toss it into a bot net which they’ll sell access to on the dark web.

    A sucker opens insecure services to the open internet every day, that’s free real estate to bot farms. Only when the probability of finding them is low enough is it not worth the energy/network costs. I think hosting on non-standard ports is probably correlated with lowering that probability below some threshold where it becomes not worth it…don’t quote me, though.

    At the end of the day, the rule is not to depend on security by obscurity, but that doesn’t mean never use it.









  • It’s an arms race, the arms just keep moving deeper into the stack system. Used to happen entirely in usermode, one process poking in and reading/writing memory of the game, so anti-cheat started keeping an eye out for malicious processes. Then at some point someone patched their kernel to cheat in a way the game couldn’t possibly detect from usermode, so someone made an anti-cheat that ran at the kernel level too.

    Modern KLA is basically a fully fledged rootkit, living in your system from boot, doing absolutely anything they can to try and make sure nothing has been tampered with. Validating signatures on bins, hooking memory mappings, watching for anything that might try to read/write the kernel or game’s memory space unexpectedly.


  • Casuals stop playing games when cheaters prevent them having fun, and it’s the casuals they need to keep happy to keep their game alive.

    IMO the answer is to internally maintain a “fun to play with” metric. It would be specific to the game, but each player’s actions and interactions with other players would be evaluated to determine how “fun” they are to play with (might need to be multidimensional, since different players like having different types of interactions). It doesn’t matter if they’re cheating, or if they’re just really good, or if they use cheesy strategies, etc, if the person isn’t fun to play with, then match them with other people who are similarly unfun to play with.

    This would cover your point that, if there’s a cheater in the lobby, and their behavior somehow makes everyone have more fun, then who cares?


  • We have memory security, virtualization and antitampering features

    As someone who games entirely on Linux and wants multiplayer to work out, the features you’re referring to are for keeping the application contained by the kernel, not the other way around. On a system where the user has full autonomy, no application should be able to know what is going on outside of its user space, and I don’t want it to.

    It’d be nice if it was a solved problem, but it’s not. From consoles to phones to windows, currently the industry relies on you not having autonomy over your device for anti-cheat to work. Every other solution is either expensive (obfuscation arms race), or untenable (real time, high resolution server side validation of every property of every player).