3 ms·
At one point I disabled the XTEST extension when I realized it could be used maliciously (sending clicks or keystrokes to applications, keylogging, etc.) XTEST
by asveikau 11y ago
At one point I disabled the XTEST extension when I realized it could be used maliciously (sending clicks or keystrokes to applications, keylogging, etc.) XTEST is already disabled by default on some distros.
After reading this I see that "xinput test Keyboard0" can also be used as a keylogger on my machine. Anybody know of a simple way to disable that one?
[PS: please no trollish answers like "use a different windowing system" :P]
- digi_owl 11y agoXinput is an extension, so it should be possible to disable via xorg.conf.
- duskwuff 11y agoXinput is a very old, very widely used extension, and handles much more than just input sniffing. Disabling it will remove a lot of really important core functionality like setting keyboard mappings and mouse acceleration. It's also likely to break certain applications which legitimately need to capture events, like screen savers.
- asveikau 11y agoYes, it's sadly ironic that things are modular enough to make xinput an extension of the protocol, but not modular enough to separate the very useful looking functionality in the xinput(1) manpage with a keylogger.
- digi_owl 11y agoOne mans keylogger is another mans debugger. Note that the command is "xinput test id". Meaning that it is a way to monitor what xinput sees when a key or button is pressed. I have personally used xev for similar purposes, map my keyboard's multimedia keys to various actions.