To read all comments associated with this story, please click here.
This is an OS issue. Not an Android issue.
You are right about this. I was reading in the Android forum and people were discussing how debugging code in the kernel was left in which pipes text entry into the shell. The debugging code should have been removed or disabled before deployment. Oops.
Besides... this is open source. Our security bugs can be as egregious as you please. But as long as a patch is released quickly we can pat ourselves on the back and collect our accolades. ;-)
Google started rolling out the patch yesterday.
Edited 2008-11-09 17:44 UTC
It's nothing to do with the kernel, other than the kernel working as designed. Input event devices are multiplexed through /dev/console and passed to the foreground virtual terminal. If you've launched a graphical environment in that terminal then the keyboard events will be passed back to it. If you also happen to be running a shell underneath that terminal, then bad things are obviously going to happen. The easy workaround is not to run a shell on that terminal. The correct one (which then works independent of the shell) is to put the console in KD_RAW mode, which prevents the passthrough of events. We hit the same issue in X during the migration from the old kbd driver to the new evdev one.




Member since:
2006-08-31
This is an OS issue. Not an Android issue.
Read the article!