I think the deal is that Linux is notoriously open sourced, such that it is somewhat difficult to think of the one without the other. Those bearing a kind of gr

I think the deal is that Linux is notoriously open sourced, such that it is somewhat difficult to think of the one without the other. Those bearing a kind of grudge may be tempted or inclined to derive a certain pleasure from the intellectual satisfaction that might come from ascertaining some personal (read: idiosyncratic) knowledge of how to entertain the 'open-sourcedness' of that mindset to an extrema. If that is so, then the vulnerability described is likely to be an issue, perhaps later, perhaps sooner, but within some given time frame during which the ubiquity of the 'net will be ever expanding. Perhaps the solution is to guide the users in some very 'user' friendly adaptation of a 'man. page' that describes with elegant confidence the methodologies germane to creating a keycode that would allow for said 'users' to give themselves the safety from the perchance nefariously driven 'code poets' who would otherwise be able to derive social insecurity from whatever access might be available to them. Long winded reply to say we need to not think about stoppping using Linux, but instead use a nice little intro for those who don't know enough (or even very little) regarding how to code a patch in their own kernel. Given that the tech will be integrating NLP more and more, I could even imagine a 'talk through' with some 'Ask Jeeves'-esque personal assistant. The whole thing is essentially a trust issue. Who's writing the code and who's debugging it to give all of the nUbs (yes, I use the old abbrev.) enough insight to give a little polish and shine to their appliances and machines. Whew, lotta writing there :d