Welcome to the first post of my new series, "Shelved Projects". In this series, I dig into the digital attic to share projects that were technicall...
For further actions, you may consider blocking this person and/or reporting abuse
@xulingfeng that was fast 😂
Red badges are my kryptonite. The moment that little red number appears in the top-right corner, my mouse just... clicks. I can't help it.🤣
Haha, same
Actually I don't know about what you are talking about but this projects is real
I can briefly give you short explanation and provide some information if you are open to this
Sure, I read up on your post, what's the flow from agreeing to assignment?
This is a gate, and a clean one. Intercepting NtCreateFile / NtCreateKey, redirecting writes copy-on-write while reads pass through, is the same shape I keep landing on from the agent side block what mutates, let what only observes through, leave the host untouched. You did it at the syscall layer instead of the tool layer. The part I’d underline for anyone building safety layers: hooking LdrLoadDll so a newly loaded DLL gets patched before it runs. That’s the failure mode most people miss. A gate that doesn’t propagate to surfaces that appear after startup isn’t a gate, it’s a gate with a hole, and the dangerous call walks straight through the new module.You and I went back and forth on “gating is too slow” before. This is the other half of that conversation. Revive it, or at least keep the LdrLoadDll propagation pattern alive somewhere.
I was quite proud of that 1 and yes, I did keep that section alive, by porting it to the agent manager for V.E.L.O.C.I.T.Y. IDE and OS, mostly for scratch files, so they execute entirely isolated. But yeah, might actually finish up Automata, it was quite fun to see it run flows across multiple notepads at once, each in their own sandbox (take this array of sentences and write each to a .txt file)