Dont think I agree, the last 14 days I have: Needed to optimize an POE exploit because a start up time of 2 min + slows down my development. Having to create values causing max number of hash collisions. Exception handling....hmm without it I can get very confused
Also, to reuse code from exploit to exploit engineering and design is a must. I can write file{ "%WINDIR%"_p / "temp" }.makeJuntionTo( objdir{"RPC Control"} ); or auto rpc = objdir{"RPC Control"}; static symlink fileA{ rpc / "file" };
-
-
because my design is made to abstract away any kind of lowlevel detail not relevant for the actual exploit. But still have total control of the resulting NT api calls.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
memory corruption based exploitation can also require algorhitmic understanding and thinking. Very much when you are creating tools: http://web.archive.org/web/20161021171216/http://www.inspectorgadget.dk/wiki/Inspector_Gadget … involved quite alot of algorhitmns
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.