Index
> Windows > Send Keys |
| Author |
|
|
revolution 29 Apr 2014, 19:06
You can only do low level key insertions if you have a kernel mode task (like a driver would be). For a normal user process you won't have direct access to the interrupt system or the keyboard buffer.
|
|||
29 Apr 2014, 19:06 |
|
|
Misery 29 Apr 2014, 19:09
revolution wrote: You can only do low level key insertions if you have a kernel mode task (like a driver would be). For a normal user process you won't have direct access to the interrupt system or the keyboard buffer. Could I achieve something with this http://waleedassar.blogspot.com.ar/2013/02/kernel-bug-1-processiopriority.html? Because of this https://drive.google.com/file/d/0B_8uzBfhUWBZS0w5cmhQZHUtNjA/edit?usp=sharing. |
|||
|
29 Apr 2014, 19:09 |
|
|
revolution 29 Apr 2014, 19:15
Maybe. But relying upon bugs is going to bite you once the bug is fixed in the next monthly update.
Just write a driver. |
|||
|
29 Apr 2014, 19:15 |
|
|
Misery 29 Apr 2014, 19:20
revolution wrote: Maybe. But relying upon bugs is going to bite you once the bug is fixed in the next monthly update. It has passed a year but, how could I do it without drivers for now? Can I set that privilege (IN/OUT) with NtSetInformationProcess? This is because I cannot send keys to a game, injecting and sendmessage does not work, so I wanted to try with this in asm. |
|||
|
29 Apr 2014, 19:20 |
|
|
revolution 29 Apr 2014, 20:17
Without a driver and without an OS bug you can't get a user mode process to do IN/OUT. This is by design. This is part of Windows being a protected mode OS. No amount of calling the undocumented native API will help you to bypass the protections (bugs not withstanding).
I would suggest another method: Debug your game and see how it is reading the keys. There is a good chance it is using GetAsyncKeyState or GetKeyState. You can inject a DLL (or patch the game) to fake the key states. |
|||
|
29 Apr 2014, 20:17 |
|
|
Misery 29 Apr 2014, 21:53
revolution wrote: Without a driver and without an OS bug you can't get a user mode process to do IN/OUT. This is by design. This is part of Windows being a protected mode OS. No amount of calling the undocumented native API will help you to bypass the protections (bugs not withstanding). I will try, but i think it is more complicated cos it's DX key. And I will try to achieve it with that bug (kernel). Thanks. |
|||
|
29 Apr 2014, 21:53 |
|
< Last Thread | Next Thread > |
Forum Rules:
|