backtop


Print 38 comment(s) - last by SkullOne.. on Nov 9 at 2:43 PM

Ban first, ask questions later

Many companies like Google Inc. (GOOG), Microsoft Corp. (MSFT), and the Mozilla Foundation reward developers with bounties of thousands of dollars for finding and exposing security flaws in their products.  Apple, Inc. (AAPL) rewards developers by kicking them out of the company's development program.

I. Tell Apple Its Security Problems, Get Kicked Out
 
Long-time Mac and iDevice hacker Charlie Miller [1][2][3] found this out the hard way this week when Apple unceremoniously revoked his developer privileges.
 
The incident occurred after Mr. Miller created an app called Instastock, which carried out a proof-of-concept attack using a bug he found in the iPhone's built-in Safari browser.  Safari, from iOS 4.3 onward, apparently was allowing unsigned code to be placed in memory and run.

Code signing is the biggest line of defense for iPhone owners.  Any app installed on the iPhone must first receive a special authorization (signature) from Apple via the App Store submission process.  While it is quite popular to turn off Apple's code signing protections in order to "jailbreak" iPhones -- allowing banned apps and forbidden customizations -- the exploits that allow this to be done also potentially allow malicious code to be executed.

For that reason, rather than gifting his discovery on the jailbreaking community, Mr. Miller instead opted to carefully test his discovery and then approach Apple about it.

Charlie Miller
Apple has banned Charlie Miller for exposing its flaws. [Source: YouTube]

Testing began with his Instastock app, which using the exploit performed innocous proof-of-concept mischief that would typically be forbidden, such as making the phone vibrate, downloading the contacts list to an attached computer, or launching an external YouTube video.

Instastock
Instastock, Mr. Miller's app, masqerades as an innocous stock tracking app [Source: YouTube]

Mr. Miller then approached Apple, giving the company fair warning and a chance to fix the bug before he published his findings at the SyScan conference in Taipei (Nov. 17-18).  Rather than politely compensate Mr. Miller for finding their mistake and warning them before a malicious party found it and attacked users, Apple instead reacted quite negatively to these developments.
 

Apple pulled Mr. Miller's app from the App Store -- which was pretty understandable given that while it wasn't doing anything outright malicious, it was using unauthorized functionality.  But what it did next was far more troublesome -- it kicked Mr. Miller out of its developer program, citing violations in the developer terms of service.

II. The Boot

Apple wrote Mr. Miller (via CNET):

From: appledevnotice@apple.com
Subject: Notice of Termination
Date: November 7, 2011 4:49:34 PM CST
To: [redacted]

Dear Charles Miller:

This letter serves as notice of termination of the iOS Developer Program License Agreement (the "iDP Agreement") and the Registered Apple Developer Agreement (the "Registered Developer Agreement") between you and Apple, effective immediately.

Pursuant to Section 3.2(f) of the iDP Agreement, you agreed that you would not "commit any act intended to interfere with the Apple Software or related services, the intent of this Agreement, or Apple's business practices including, but not limited to, taking actions that may hinder the performance or intended use of the App Store or the Program". Further, pursuant to Section 6.1 of the iDP Agreement, you further agree that "you will not attempt to hide, misrepresent or obscure any features, content, services or functionality in Your submitted Applications from Apple's review or otherwise hinder Apple from being able to fully review such Applications." Apple has good reason to believe that you violated this Section by intentionally submitting an App that behaves in a manner different from its intended use.

Apple may terminate your status as a Registered Apple Developer at any time in its sole discretion and may terminate you upon notice under the iDP Agreement for dishonest and misleading acts relating to that agreement. We would like to remind you of your obligations with regard to all software and other confidential information that you obtained from Apple as a Registered Apple Developer and under the iDP Agreement. You must promptly cease all use of and destroy such materials and comply with all the other termination obligations set forth in Section 12.3 of the iDP Agreement and Section 8 of the Registered Developer Agreement.

This letter is not intended to be a complete statement of the facts regarding this matter, and nothing in this letter should be construed as a waiver of any rights or remedies Apple may have, all of which are hereby reserved. Finally, please note that we will deny your reapplication to the iOS Developer Program for at least a year considering the nature of your acts.

Sincerely, Apple Inc.

Mr. Miller quickly fired off a post to Twitter, commenting:

OMG, Apple just kicked me out of the iOS Developer program. That's so rude!

The post drew the sympathy of Microsoft developer relations officer Brandon Watson who offered Mr. Miller a free developer subscription on Microsoft's Windows Phone platform, writing:

Hey #0xcharlie, sorry iOS credentials went missing. Want a free Windows Phone dev account? #wpdev folks love the platform.

Of course Mr. Miller is likely going to keep on hacking Apple devices, but the Microsoft post is a clever bit of PR in that it helps illustrate the major difference in approach between Apple and Microsoft -- or Apple and most software firms, for that matter.

This incident isn't terribly surprising for a company that reportedly ordered its employees to lie to customers about malware and who steadfastly insists that its devices are too "magical" to be vulnerable to traditional attacks.

Sources: Charlie Miller, Brandon Watson (Microsoft), CNET



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

RE: Interesting turn of events
By cochy on 11/8/2011 9:48:24 AM , Rating: -1
He was kicked out because he circumvented the iOS developers terms of service by uploading that app. It's a pretty black and white issue here.

He could have approached this differently.


RE: Interesting turn of events
By blankslate on 11/8/2011 11:46:57 AM , Rating: 2
quote:
He could have approached this differently.


Apparently he notified Apple of the exploit and then waited for a reply from them acknowledging the issue and that they were working on it.
We know from past experience that Apple has become aware of a security issue and ignored it for months before fixing it.
Apple even instructed tech support employees to pretend a piece of malware didn't exist instead of helping callers remove it.

Considering Apple's attitude of pretending to the general public that security problems affecting Apple products are fairy tales, I don't blame Charlie Miller for uploading the proof of content app after giving Apple a few weeks to fix the problem (even if just temporarily.

Apple could have approached this differently and they damn well should have.


RE: Interesting turn of events
By Fritzr on 11/8/11, Rating: -1
RE: Interesting turn of events
By blankslate on 11/8/2011 2:23:37 PM , Rating: 2
It seems to me that you're ignoring the point that Apple has a demonstrated propensity to ignore security problems.

If they had acknowledged the problem and replied to Mr. Miller "Thanks for notifying us of the issue we will start working on it." or "We are aware of the issue please keep this confidential while we work on a solution."

From what I understand from reading interviews with Charlie Miller; if Apple had replied with acknowledgement of the problem and actually devoted the required resources to fix it in a timely manner he would've waited until after Apple fixed the problem to go public with how he discovered the problem.

You are right Apple had every right to ban Charlie Miller after he uploaded the app.

However, in this case Jason Mick is also right
quote:
The real question people should be asking here is not "Was Apple within its rights to ban the dev?", but rather "Was Apple behaving responsibly and protecting its customers?"


Apple has shown in the past and in this case that they don't behave responsibly when it comes to protecting it's customers from people who might attempt to exploit Apple products.


RE: Interesting turn of events
By Solandri on 11/8/2011 3:49:43 PM , Rating: 5
quote:
These three were triggered by his official submission of an app to be included in the AppStore following review of the app and the supporting documentation.

The app was submitted & approved based on the description supplied to Apple -- important information was omitted from that application. This is a violation

The app was DESIGNED to use functions in a manner not permitted by the TOS or mentioned in the description of the app's behavior. This is a violation

The developer used flaws in Apple's software to perform functions not permitted by the TOS. This is a violation.

Unfortunately, because Apple controls the only way to get apps signed and onto your iPhone, the only way to get an exploit like this tested is to violate the TOS. The reason the TOS prohibits the activities you listed is (ostensibly) to keep App Store users safe. The reason Mr. Miller submitted the software to test the exploit was to keep App Store users safe. He violated the letter of the TOS to uphold the spirit of the TOS.

If Apple truly believes in keeping its users safe, it should have seen that, thanked him, and fixed the security hole. Booting him from their developer program (assuming it wasn't a mistaken knee-jerk reaction by some low-level underling) indicates that Apple does not believe improved user safety is the true reason for keeping the App Store locked down tight. That there is another reason for keeping it locked down which supersedes user safety.


"This is about the Internet.  Everything on the Internet is encrypted. This is not a BlackBerry-only issue. If they can't deal with the Internet, they should shut it off." -- RIM co-CEO Michael Lazaridis














botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki