Programatically trapping .DLL/.EXE loading to grant access or deny at low-level
Posted on 2006-05-02
I'm an experienced programmer but windows kernal stuff is beneath me. Is there a 'right' way to undermine the window's kernel's .DLL and .EXE (and .OCX, etc) loading logic before the .DLL or .EXE is loaded? Perhaps to return an error 5 (Access Denied) if my checks are not met.
Obviously this has hacking potential but my intents are angelic I promise. Administrative installation access is a given and obviously required.
I'm not sure if a device driver, dll replacement to hook calls, or what is the best or 'most correct' way to handle this.
This is a tough question and somebody with key kernal knowledge is needed for advice.