Date: 2016-04-22 06:13 am (UTC)
From: [personal profile] mjg59
It'd be pretty easy to avoid the obvious cases - block anything that calls XSelectInput() or XTestFakeKeyEvent(), but people aren't obliged to call the library functions to do this. You could write some pretty obfuscated code that would end up having the same result, and that would filter through any kind of checks that could reasonably be implemented. It's a hard problem - the only way to really handle it is to design the technology such that these attacks aren't possible in the first place.
Identity URL: 
Account name:
If you don't have an account you can create one now.
HTML doesn't work in the subject.


If you are unable to use this captcha for any reason, please contact us by email at

Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.


Matthew Garrett

About Matthew

Power management, mobile and firmware developer on Linux. Security developer at Google. Ex-biologist. @mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer.

Expand Cut Tags

No cut tags