No.14437
Found this:
When you type on your keyboard, it looks like the keystrokes are directly sent to the application you're working on. In reality, they have to go through quite a long path to get there.
The keystrokes first arrive at a hardware controller on the computer's motherboard, which forwards them to the Windows kernel's keyboard input stack. They are then processed by the windowing system's input manager, which sends them to a queue belonging to the application window that currently has input focus.
The application then retrieves the keystrokes from the queue and interprets them according to its own context, and finally the user sees the result of the keys that are pressed. This is a simplified view of what happens, without considering such complex issues as inputting non-English languages.
Many places along this path, there are ways to intercept the keystroke data. Any of these points can be used to perform keylogging, which is why it's such a thorny problem.
What KeyScrambler does is to try to get to the keystrokes as early as possible in the Windows kernel using our encryption module. That way, as they get passed along the different layers of the OS, it won't matter if they get logged, because the keystrokes are completely indecipherable.
When these encrypted keystrokes finally arrive at the intended application, the decryption component of KeyScrambler goes to work and turns them back into the keys the user originally typed.
If you are familiar with how SSL/TLS work to encrypt network traffic, this is basically the same principal applied to your keystrokes.
>Anyone with knowledge, how safe does this sound? - why can't key loggers grab from the same low level place?
