Directory filtering needs to be fixed, one weird filename or symlink will make it BSOD.

SSDT should probably have a lock. The chance of a race is ~low (higher under heavy sustained workloads) but it's too important to leave to chance.

I'd probably do a rebuild of the directory lists in a separate buffer instead of working in place to avoid alignment fuckups.

Yes I used LLMs, just like I did for all of the other vulns I've found or refined. As you can see from the source, this shit is tedious as hell. Doesn't change the value of knowing what to look/ask for.

Give one of those open models a fresh windows box (not a VM) and tell it to fuck something up, it's fun.

▲

joshka 4 hours ago | parent [-]

If you're using coding agents for this, it may be worth splitting this up into multiple well arranged modules that tell a coherent story and make it easy to browse, and add explanatory docs based on the various things the LLM has found about each function / type.

▲

monster_truck 4 hours ago | parent [-]

Waste of tokens IME, better to do it like this and leave that kind of post processing to signature obfuscation.

You don't need exploratory docs, try asking one for complete function signatures of all the Windows APIs used, it's going to spit the docs out.

	▲	joshka 2 hours ago \| parent [-]
		Your decompilation threads have all the necessary info in them for this, anyone coming after lacks that foundation and effectively is doing a second inference over the hidden state, assumptions, etc. that your sessions have in them. A simulacrum of a simulacrum in essence is likely to be not particularly good.