用于DeviceIOControl的SetWindowsHookEx,将使用哪个hookid? [英] SetWindowsHookEx for DeviceIOControl, what hookid to be used?
本文介绍了用于DeviceIOControl的SetWindowsHookEx,将使用哪个hookid?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
HHOOK WINAPI SetWindowsHookEx(
_In_ int idHook,
_In_ HOOKPROC lpfn,
_In_ HINSTANCE hMod,
_In_ DWORD dwThreadId
);
在MSDN上列出的可用idHook值中,有:
On MSDN listed available idHook values, there are:
- WH_CALLWNDPROC
- WH_CALLWNDPROCRET
- WH_CBT WH_DEBUG
- WH_FOREGROUNDIDLE
- WH_GETMESSAGE
- WH_JOURNALPLAYBACK
- WH_JOURNALRECORD
- WH_KEYBOARD
- WH_KEYBOARD_LL
- WH_MOUSE
- WH_MOUSE_LL
- WH_MSGFILTER
- WH_SHELL
- WH_SYSMSGFILTER
那么,应该使用什么idHook来钩挂DeviceIOControl函数(对于控制台应用程序)?还是我可以使用其他钩子方法?
So, what idHook should be used for hook DeviceIOControl function (for console application)? Or may i'd use some other hook method?
推荐答案
DeviceIOControl
用于与驱动程序进行交互,并且在用户模式下提供的非挂钩窗口允许挂钩驱动程序交互,而最好将使用Windows DDK/WDK/Windows SDK(取决于您所针对的Windows版本)编写过滤器.
DeviceIOControl
is for interacting with drivers, and non of the hooks windows provides in user mode allow hooking driver interaction, instead you best best would be to write a filter using the windows DDK/WDK/Windows SDK (depending what windows version you are targeting).
这篇关于用于DeviceIOControl的SetWindowsHookEx,将使用哪个hookid?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文