not sure why you quoted me. here my 2 cents.Seriously what developer who knows anything about security is going to download an IDE from a non official source?
That's like downloading an OS from The Pirate Bay and being shocked the file was injected with malicious code.
Mercury - if it is the web browser - that is huge. Mercury is on a lot of devices.
No, it doesn't, because once Apple recognizes that kind of a problem, they can also fix it from that one central location. Without that "walled garden" approach, every user would now have to install a malware scanner and hope that it will get updated with profiles for the new malware.If infected apps can pass through Apple's iOS app gates it undercuts Apple's security rational for insisting on a Walled Garden.
How could Apple have avoided that situation? How did Apple betray its users? Apple did not force anyone to download a compromised Xcode version. The only "mistake" Apple made was not to recognize the malware in the review process. But that is hardly trivial.Admittedly I know zip about coding but seems Apple is betraying it's users here and could have avoided this situation. I Hopefully this is a wake up call.
So... It begins.
iOS has been breached through the one thing that kept us safe. The App Store.
Yep, Data Monitor is still there too. Last updated in 2014. I certainly hope Apple is on the case and will address this asap.If this only affects past versions of some apps, it would be nice to know exactly which version #s of each app are affected.
EDIT: For WeChat at least, it seems we do know that! The source document says 6.2.6 is fixed.
I don't think that's a correct analysis of the situation.
What has really happened here? Developers have used the wrong tool (we'll discuss that later) and that tool has embedded some unwanted additional code in their apps. BUT look what still worked
- each broken app STILL has to be submitted to the app store, with identification and an audit trail
- even when the app is on an iOS device, there are severe limits to what it can do. It still can't break out of the OS protections, randomly control the device, etc. The type of info being sent back to base is, let's face it, not THAT serious --- not ideal, but not control of the machine.
- The items that ARE problematic (and which Apple should work on fixing) are items that were problematic before we knew about this, and that have been used in other contexts --- the ability to phish for passwords by throwing up fake dialog boxes, and the way the current sandboxing FORCES Password apps like 1Password to transfer data over the Clipboard.
What this REALLY provides is a way to throw out a bunch of these phishing scams in a way that can't be traced back to the real scammer; only to the developer using the wrong tool.
Which gets us to that issue. I don't know enough about XCode to know what was and was not breached on that front. Obviously the entire XCode package should be signed, and obviously if you're stupid enough to install an XCode package that complains about being unsigned, you're setting yourself up for trouble. But blaming the victim, especially when the security landscape changes every year is not helpful --- how could Apple do better?
You can't really avoid people being able to write their own compilers and dev tools, and you can't stop those dev tools from doing god knows what to the code they create --- this has been known since Pike's infamous C compiler of the early seventies.
What you SHOULD be able to do is not allow code that has been created by such dev tools into the app store. THAT seems to be the flaw that needs to be fixed --- that any tool that's generating binaries that will land up in the store needs to be provably signed. But I don't know how feasible that is. Obviously the last stage (the actual store submitter app) is provided by Apple and signed, and using the developers signature. But what about the linker beforehand? And the compiler before that? And you then need the binaries passed between the two to be encrypted? It's just totally inimical to the current expected model of how we code.
So what about at a higher level? Do something that's a ugly hack, but basically FORCE that any installer that calls itself "XCode" has to be signed no matter what? That's one package that you can't install regardless of your GateKeeper settings except from Apple. But then you get a wack-a-mole of packages called "XCode 7" and "XCode!" and "XCode Pro".
How could Apple have avoided that situation? How did Apple betray its users? Apple did not force anyone to download a compromised Xcode version.
Yep, Data Monitor is still there too. Last updated in 2014. I certainly hope Apple is on the case and will address this asap.
Because the connection is very slow and Xcode download is very large. But makes me wonder why Apple doesn't make these downloads available from Chinese servers (I assume they don't).Why would anyone download Xcode from anyone other than directly from Apple? Even if the download is slower it can't be worth getting a compromised developer tool.
the way the current sandboxing FORCES Password apps like 1Password to transfer data over the Clipboard.
I feel the same way. It is incomprehensibly stupid. I don't care if it takes a week to download Xcode, as a professional developer that distributes applications to potentially millions of users, downloading from anywhere other than the source is just ridiculous. I'm shocked at WeChat. Never using that app again.My thought is I am all done with any company that would use an Xcode version they got from a file sharing site rather than Apple directly. I would never trust them again.
I used WinZip on iOS
But i also bought it in the Mac App Store. Any guarantees that the Mac Version is not infected?
It is irresponsible and unprofessional. Wouldn't mind if Apple remove those developers and their products completely from the app store.I don't care if it takes a week to download Xcode, as a professional developer that distributes applications to potentially millions of users, downloading from anywhere other than the source is just ridiculous.
You'd be surprised by the amount of companies using pirated apps.If this only affects past versions of some apps, it would be nice to know exactly which version #s of each app are affected.
EDIT: For WeChat at least, it seems we do know that! The source document says 6.2.6 is fixed. (Although using ANYTHING from Tencent sounds risky, if they're willing to use developer tools downloaded from untrusted servers instead of from Apple. Big company... can't get the real tools?)
I agree, that is absolutely ridiculous and shameful for those developers. And all to save a few minutes on the download? Come on. Go eat lunch while it downloads (that's what I do for Xcode updates) or do it overnight if necessary, but no good developer would download their main dev environment from any file sharing site. I'd say they deserve what they get but millions of users are going to pay the price for their laziness.Seriously what developer who knows anything about security is going to download an IDE from a non official source?
That's like downloading an OS from The Pirate Bay and being shocked the file was injected with malicious code.