Risk
9/8/2011
05:29 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Android Survey Highlights Piracy Problem

Yankee Group and Skyhook Wireless issue report that faults Google for failing to do enough to prevent unauthorized app copying.

Top 15 Google Apps For Business
Slideshow: Top 15 Google Apps For Business
(click image for larger view and for full slideshow)
Android developers make less money from paid apps than iOS developers, a disparity that appears to be attributable to software piracy.

The Yankee Group, a consultancy, and Skyhook Wireless, a mobile location data company that's currently suing Google for excluding its geolocation system from Android devices, have surveyed 75 Android developers and found that they don't earn as much revenue as iOS developers and that they blame the gap, at least in part, on piracy.

Some 27% of those surveyed see piracy as a "huge problem" and 26% say it's "somewhat of a problem." And 53% believe Google isn't doing enough to mitigate the damage caused by unauthorized app copying.

About a third of respondents characterized the damage done as more than $10,000 annually and about as many said that piracy increases their support costs. Some 25% reported increased server costs associated with pirated apps.

Complaints about piracy in the Android Market aren't exactly unheard of. Last year, Android software marker KeyesLabs noted that the overall piracy rate for its app Screebl Pro was 67%.

Google does provide a License Validation Library (LVL) that allows developers to determine whether an Android Market app has been acquired legitimately or not, but respondents complain that the LVL is easy to defeat without additional copy protection techniques and that such techniques generally alienate legitimate users.

"[S]oftware piracy is a tremendous problem concerning Android apps, especially if apps act as a background service," said Android app maker SmartDyne in the report. "The Google license server policy is not satisfying all needs. In many countries, data flat rates are either not available or are very expensive so users tend to deactivate the mobile data connection. As a result, background services become unavailable from time to time. The only solution is a license key policy based on accounts and/or device IDs. But this results in higher effort for every purchased app and of course higher costs."

Stating that "Android apps live in the Wild West without a local sheriff," the Yankee Group proposes several specific steps Google could take to deal with app piracy. These include establishing a market certification program to allow customers to tell good Android markets from bad ones, providing a way to verify that an app has been paid for online, and building a system that provides automatic code obfuscation and tamper checking for Android apps.

David Keyes of KeyesLabs offered a similar proposal in the Android developer forum. "Google could do better, and I hope that they will," he wrote. "Obfuscation isn't really going to do much to improve the situation. What is really needed is O/S-level and app store support for signing apps (in real-time) based on user credentials, application authors, and phone characteristics. The dependence on the Android Market app is a single point of failure that is too easy to search for and find regardless of how obfuscated your code is."

Google did not respond to a request for comment.

Attend Enterprise 2.0 Santa Clara, Nov. 14-17, 2011, and learn how to drive business value with collaboration, with an emphasis on how real customers are using social software to enable more productive workforces and to be more responsive and engaged with customers and business partners. Register today and save 30% off conference passes, or get a free expo pass with priority code CPHCES02. Find out more and register.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-5084
Published: 2015-08-02
The Siemens SIMATIC WinCC Sm@rtClient and Sm@rtClient Lite applications before 01.00.01.00 for Android do not properly store passwords, which allows physically approximate attackers to obtain sensitive information via unspecified vectors.

CVE-2015-5352
Published: 2015-08-02
The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time ...

CVE-2015-5537
Published: 2015-08-02
The SSL layer of the HTTPS service in Siemens RuggedCom ROS before 4.2.0 and ROX II does not properly implement CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, a different vulnerability than CVE-2014-3566.

CVE-2015-5600
Published: 2015-08-02
The kbdint_next_device function in auth2-chall.c in sshd in OpenSSH through 6.9 does not properly restrict the processing of keyboard-interactive devices within a single connection, which makes it easier for remote attackers to conduct brute-force attacks or cause a denial of service (CPU consumptio...

CVE-2015-1009
Published: 2015-07-31
Schneider Electric InduSoft Web Studio before 7.1.3.5 Patch 5 and Wonderware InTouch Machine Edition through 7.1 SP3 Patch 4 use cleartext for project-window password storage, which allows local users to obtain sensitive information by reading a file.

Dark Reading Radio
Archived Dark Reading Radio
What’s the future of the venerable firewall? We’ve invited two security industry leaders to make their case: Join us and bring your questions and opinions!