Keylogger project problems.

[Torahteen]

Aaaah, c'mon...




:wink:

[Agamemnus]

A simple solution for security purposes should be to simply disable the key logging function in the windows API... or, if the key pressed were global, have the information available only in the exe where it's inputted. Wouldn't that actually make some sense from a programming standpoint? :roll:

[Anonymous]

there is no "keylogging funtion" in the api. the api allows you to retrieve what keys were pressed. disabling that would disable all programs that use the api to collect keystrokes (tons)

really, thank god its not as easy as caling a function. imagine how many Le3t hakxorz we'd have then :roll:

[na_th_an]

The key logging is so easy to achieve. What's difficult is "hiding" the program.

[red_Marvin]

I just hope this has noting to do with the "taking out the internet"
thread :p

[KiZ]

The key logging is so easy to achieve. What's difficult is "hiding" the program.

That aint difficult!

just compile "-s gui" and make sure you dont call SCREEN

[Torahteen]

Kiz, but could you log keys that aren't being typed into that program? Is the Inkey buffer a global one?

[na_th_an]

It isn't.

The trick is to have that program running in foreground all the time. There are some dirty hacks to be able to do this. Then you must bring to foreground the program which was on there when you ran your keylogger, and use Windows API's "sendkeys" to send it the stored keypresses so the user doesn't notice that something is trapping them. It's tricky, but it's doable.

Another technique would be having the program itself running in the background with a thread "listening" to the keyboard. You can even use directInput to make your life easier.

Anyway, what KiZ describes would not hide the program at all as it would show as a process in the task manager list

[DrV]

The best way to do something like this is with a system-wide keyboard hook, which I'm sure MSDN will be able to tell you more about if you're so inclined. Hopefully it's complicated enough that you'll give up (we can only hope).

[na_th_an]

Funny how the #1 resource to learn how to write malware is the MSDN itself :lol: