![]() |
Android kernel: revealed 359 software defects
Interesting:
"# The Android kernel tested by Coverity revealed 359 software defects, which is a sample of what might be shipping in popular mobile and other Android-based devices. # 25 percent of the Android defects found are high risk with the potential to cause security breaches and crashes." http://www.coverity.com/html/press/c...n-android.html I wanted to say "I know why I do not use Android" ;-) but otoh: do we have such analyses for Maemo? |
Re: Android kernel: revealed 359 software defects
The android kernel is Linux kernel, probably most of those "defects" are in Maemo as well.
And defining a flaw that can give a user root access as "high risk" on a single user machine, where user can do practically anything, including sending all your private data anywhere and cost you any sum in fees and the only addition thing root can do is to require a 5 minutes reflash of the system, is nothing but a cheap publicity stunt. |
Re: Android kernel: revealed 359 software defects
Quote:
Quote:
|
Re: Android kernel: revealed 359 software defects
I'm waiting for the attack of desktop sheep roaming around on the n900 - like on windows in the 90's.... oh the joys :) (Process killer, but genius to watch as the single sheep multiplies into 10,000 and windows topples over!)
|
Re: Android kernel: revealed 359 software defects
Quote:
Quote:
|
Re: Android kernel: revealed 359 software defects
Not to mention that you cannot, theoretically, declare any potential NULL dereference pointer found in a static analysis of source code a "security issue". At most, it is a potential one.
|
Re: Android kernel: revealed 359 software defects
> At most, it is a potential one.
Never, ever marginalize the effect of an invalid pointer in kernel space. |
Re: Android kernel: revealed 359 software defects
Quote:
|
Re: Android kernel: revealed 359 software defects
Quote:
:D |
Re: Android kernel: revealed 359 software defects
Quote:
Code:
struct some_interface *c = get_from_global_variable(); a ) Either detect a "potential NULL dereference", thus indicating that the 5000000 potential bugs found count is pure crap. b) Do nothing. I do not know which one is worse! c) Somehow magically deduce all posible code paths and follow them all to detect where the actual bug is. The list of all available code paths does not only depend on hardware configuration but might actually even depend on the current time. Not to mention the above is a pretty common idiom, specially if, as according to the makers of this tool themselves, "dereferencing function pointers is quite common on the kernel". Quote:
Now on Maemo getting root is usually as easy as running any of the numerous setuid binaries or sudoers-listed programs, so I can understand why it doesn't matter. On other platforms, maybe that's not true. On WebOS at least, _every application_ already runs as root by default, and there was no normal user at all until a recent version. Now, of course their tools ain't cheap. They're doing a great service to the community IMHO but also getting some free marketing for a tool a decade or two ago would be laughed at. Note: not saying it is useless; it's as useless as getting a human to do it: they might get it wrong, but "the more eyes...". |
All times are GMT. The time now is 12:58. |
vBulletin® Version 3.8.8