not_a9
not_a9 on Hacker News
The next choice will be dynamically resolving syscall IDs from NTDLL? Surely that has no issues that could possibly happen.
If you look at unknowncheats.me you’ll see a significant amount of reversing of their games
Plenty of function pointers to overwrite, presumably
For what it’s worth isn’t liquid metal actually not very good for extreme overclocking seeing as it solidifies at subzero temps?
Do you think Deadlock will not devolve into a mixture of gambling and hvh like every Valve multiplayer game that’s been relevant in the last 10 years (except Dota because hvh in dota sounds complex, so it's just gambling there)?
Fortnite avoids this by having no gambling and by making hvh infeasible FYI
> They clearly know what they are doing at Valve
Yeah, at promoting child gambling. Not sure about games
What ranks are you playing on? While a player of any rank can buy Neverlose and win and if they wanna just pwn cleans they can buy Midnight (speaking of buying P2Cs: if Faceit is apparently riddled with cheaters, where can I buy a P2C that I can pwn on Faceit with for an affordable price?), said cyber athletes will naturally gravitate towards higher ranks.
> FACEIT is riddled with cheaters
According to sources of… what? In any case it’s sure as shit less riddled with cheaters than Premier LMAO
Most likely there’ll be lots more hunting for physmem read/write vulnerabilities as well as bugs in userspace stuff like GUI whatsits that’d give code execution/memory readwrite.
Userspace bugs is where I’d look first.
How is Valve’s VACNET doing? I think you should take a look at what’s happening in Counter-Strike 2 these days to see what the true frontier of ML based anticheat looks like.
Frankly at this point I’m pretty sure John McDonald plays HvH too
I can't edit this post anymore but if you wanna read a bunch of stuff on the topic
https://k0mkc.hatenablog.com/ is a nice blog. All in Japanese, but it should be perfectly translatable.
Funny thing is they removed all their blogposts on Griffin (an obfuscator several anticheats, including EA's, Riot's and FaceIT's utilize) for whatever reason.
Devirtualization and recompilation is unfortunately a really, really tough task even for clank assisted RE.
Unlikely most of the Denuvo cracks actually remove the virtualized code from the executable. Not feasible without extensive binary rewriter tooling (that, while being sloppable, still takes a lot of time to slop).
I don’t think most obfuscators will care about self-modifying code anyway, outside of cases like packing (…and in that case you probably won’t be rewriting the unpacker stub anyway :D). Also self modifying code breaks on targets like Windows kernel drivers, which are a big target for SOTA obfuscation these days.
Technically most malware should generally be able to rely on the syscall interface, no? As generally it doesn’t need a GUI or anything
Visual Studio does have a really nice C++ debugger - one would imagine the C++ debugging capabilities should translate to Rust.
> PS C:\Program Files\Microsoft Visual Studio\18\Community> dumpbin.exe /EXPORTS C:\Windows\System32\ntdll.dll | rg ZwMapViewOfSection
2072 80F 001612B0 ZwMapViewOfSection
2073 810 00163160 ZwMapViewOfSectionEx
> PS C:\Program Files\Microsoft Visual Studio\18\Community> dumpbin.exe /EXPORTS C:\Windows\System32\ntdll.dll | rg NtMapViewOfSection
425 1A0 001612B0 NtMapViewOfSection
426 1A1 00163160 NtMapViewOfSectionEx
> How "differently" exactly? That's undocumented.
https://learn.microsoft.com/en-us/windows-hardware/drivers/k...
Given the cost of openweight frontier models like Kimi I’m fairly sure the token prices actually make some money.
> This has nothing to do with ntdll at all.
I can only wonder where `NtMapViewOfSection` could be exported from...
I wonder how they handle merging upstream clanked stuff.
Memories break Fable 5 for me as well in chatbot. I ask Opus a lot of sec related stuff and now if I even type “hello” in chat it gets insta-downgraded to Opus 5.
Assuming you want to preserve the same functionality of drivers, how would giving the userspace RGB controller driver the same set of tools (usually fun things like physical memory RW) change anything?
Microsoft did break backwards compatibility with some drivers (packed stuff that relied on being able to write to executable sections, for instance) w/ HVCI and then with some other stuff (for instance, drivers using push+ret for obfuscating function calls + some exception handling related machinery some virtualization based obfuscators used) with KCET.
With that being said virtualization based security is not mandatory, though compliance is needed for signing new drivers (note: this is funky too and some drivers will do HVCI-noncompliant things when it’s disabled, like some anticheat drivers hooking #PF to more efficiently catch unsigned code execution in HVCI-free scenario). I think next backwards compatibility breaking move will be enabling SMAP.
Technically the hardware threshold is sort of real for making virtualization based security usable and useful.
The significantly increased capabilities of cheats if you can read/write memory and the dogshit that AI-oriented anticheat approaches continue producing (look at VACnet, though I am sure there are other companies producing better things like Anybrain - the thing is, 99% of the time the products of said companies are integrated along with a proper strong anticheat like EAC) will ensure kernel mode anticheats will be alive and well.
While I’m not sure if this is a bot (where did vidya enter the convo?), game hacking on both cheat and anticheat side has genuinely deep Windows internals knowledge (admittedly somewhat lopsided, but deep nonetheless)
OK, but is that fun for people who don’t wanna clankermaxx? In addition this does not address the paytowin aspect of clankermaxxed CTFs