I've read somewhere ia_32_sysenter holds the offset which is loaded into EIP when sysenter is executed, is there any kind of stealth,best method of kernelhooking when the purpose is monitoring the value of EAX when sysenter is called?
A forum for reverse engineering, OS internals and malware analysis
lorddoskias wrote:I don;t think it is useless. It certainly raises the bar. Recently there hasn't been any rootkits which targeted patchguard explicitly, by explicitly I mean circumventing the actual DPCs etc, rather they all try to disabled it even before it has started so I'd say it is effective to a certain extent.Yes, I agree. Patchguard does not make kernel hooking impossible. However, it probably discourages many to do so. People use documented methods to solve their problems, there is much less amount of data and code modifications, so the whole kernel should be more stable.
Vrtule wrote:lorddoskias wrote:I don;t think it is useless. It certainly raises the bar. Recently there hasn't been any rootkits which targeted patchguard explicitly, by explicitly I mean circumventing the actual DPCs etc, rather they all try to disabled it even before it has started so I'd say it is effective to a certain extent.Yes, I agree. Patchguard does not make kernel hooking impossible. However, it probably discourages many to do so. People use documented methods to solve their problems, there is much less amount of data and code modifications, so the whole kernel should be more stable.
listito wrote:thanks, imho patchguard is almost useless, trying to protect windows kernel with ring0 code is stupidCan you justify your point?