Commentary

Serdar Yegulalp
 

Android Is (Or Was) Insecure? Don't Panic

After news broke the other day that Google's Android handset development library had several vulnerabilities that could be exploited by an attacker, I braced for a flood of "Told you so!"-type announcements.  Frankly, the fact that these problems have shown up at this stage in the development process isn't a bad thing. This is the best possible scenario.

After news broke the other day that Google's Android handset development library had several vulnerabilities that could be exploited by an attacker, I braced for a flood of "Told you so!"-type announcements.  Frankly, the fact that these problems have shown up at this stage in the development process isn't a bad thing. This is the best possible scenario.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The first and most obvious thing to get out of the way is that the Android libraries are all still very much a beta product.  Nobody's created a commercially available device that uses the library (yet), so any attacks that could be carried out wouldn't affect anyone except the people doing development.  In fact, this problem already has been fixed in the most recent release of the platform build.

The fact that problems have turned up at this stage isn't a bad thing.  When the development of a project this large and attractive is done out in the open, instead of behind closed doors, there are that many less mysteries about what might go wrong -- and what could be used against the people who depend on it.  It also means the developers are beholden to the public as a whole to fix these problems, not internal pressures.  The system's working as intended, and that's the best news of all.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links