1

Topic: keylogger

What methods are to intercept , level more low WH_KEYBOARD_LL, but still in ? That is there is an application which already puts "  on " - SetWindowHookEx (WH_KEYBOARD_LL and processes all input and further does not start up ( that above level - type simply  on , rawinputdevice - already events do not receive). The task in that all the same be weighed-ve input to direct also also to our application. thanks in advance

2

Re: keylogger

Hello, sr_dev, you wrote: _> what there are methods to intercept , level more low WH_KEYBOARD_LL, but still in ? _> that is there is an application which already puts "  on " - SetWindowHookEx (WH_KEYBOARD_LL and processes all input and further does not start up ( that above level - type simply  on , rawinputdevice - already events do not receive). _> the Task in that all the same be weighed-ve input to direct also also to our application. _> thanks in advance it is possible to look aside  at functions user32.fnHkINLPKBDLLHOOKSTRUCT which is responsible WH_KEYBOARD_LL for the pointer on it is in the table apfnDispatch which Peb-> KernelCallbackTable about it is a little here here again well and IDA to you in the help and a source code win2k!

3

Re: keylogger

Hello, sr_dev, you wrote: _> what there are methods to intercept , level more low WH_KEYBOARD_LL, but still in ? _> that is there is an application which already puts "  on " - SetWindowHookEx (WH_KEYBOARD_LL and processes all input and further does not start up ( that above level - type simply  on , rawinputdevice - already events do not receive). _> the Task in that all the same be weighed-ve input to direct also also to our application. _> thanks in advance I think, it is necessary  the application putting  therefore as delivered last  works the first. Further it will be necessary to define what window of input now actively to send it the message. In the end not to forget to cause CallNextHookEx There is also a second, more hacker and is dirty-perverted method - to intercept calls SetWindowsHookEx and to organize the pool  with  and women with the under social responsibility, solving whom that it is possible to do. The theory and example of the ready code it is possible to look, for example in Dzhefri Richter's book "Creation effective Win32 applications" .22 "DLL injection and interception of API-calls".

4

Re: keylogger

Hello, Maniacal, you wrote: M> Hello, sr_dev, you wrote: M> I Think, it is necessary  the application putting  therefore as delivered last  works the first. Further it will be necessary to define what window of input now actively to send it the message. In the end not to forget to cause CallNextHookEx the  it is necessary to rearrange periodically, other program-output agent of input restart after all can M> There is also a second, more hacker and is dirty-perverted method - to intercept calls SetWindowsHookEx and to organize the pool  with  and women with the under social responsibility, solving whom that it is possible to do. It would be desirable to avoid a porno (while)

5

Re: keylogger

Hello, sr_dev, you wrote: _> what there are methods to intercept , level more low WH_KEYBOARD_LL, but still in ? Above or more low I do not know, but keypad interception so is implemented through: Raw Input AttachThreadInput GetAsyncKeyState

6

Re: keylogger

Hello, sr_dev, you wrote: _>  it is necessary to rearrange the periodically, other program-output agent of input restart after all can It is possible to try  with function RegisterForDeviceNotifications, it, like as, can intercept the keyboard data at a transmission stage through USB/PS2. Deeply did not dig, but Google says that interception of keyboard input by this function quite normal approach, but mentions of that that more low-level,  or interception of messages from devices, no. Plus (truth, it it is possible, invisible) presence of the window of top level is necessary for usage in quality  for RegisterForDeviceNotifications.