Quote:
Originally Posted by geekmaster
Now I am curious about that " mxckpd" device driver that they bothered to load on the touch.  |
I think it's a userland interface to re-insert key events into kernel space. But just guessing here. Depending on preferences, it is the easiest approach to implement a software-keyboard that ought to be working on a not-yet-fully-determined target framework. It won't even be X-specific then, you could implement the software keyboard as a raw-framebuffer application and generate events for all UI things on the device.
What I meant above, BTW, is to listen for all events (on all devices) and then handle the events you care about. E.g. keypresses, touchscreen events etc. Trust them to generate certain key codes/event values, don't bother with addressing.
Of course you're right that physical access is always the biggest threat to the security of a computer. Well, but the physical access path isn't something I would worry about on my Kindle. If someone took it from me, I'm not trusting it anymore as a computing platform anyway. And don't think you could lure me into soldering a connection cable to a 1V8 TTL controlled rubberduck on my ebook reader :-P