This should have been fixed back in July when they were told about it.. So this is no excuse. But this should have been fixed the latest by monday night.. Its a double no excuse...
this is totally something my mom would fall for lol
This should have been fixed back in July when they were told about it.. So this is no excuse. But this should have been fixed the latest by monday night.. Its a double no excuse...
Why is there even a government warning. Don't download random apps from third party app store, duh. Who does that anyway.
----------
I bet she gets hacked on her windows computer all the time.
"unlikely to affect the average iOS user so long as Apple's security features are not bypassed"
Problem solved. Huge deal for nothing.
If the US government is putting out an official warning, then it's not being blown out of proportion.
I have no definitive answer, but I know that you don't need a certificate already installed to download other apps from outside the App Store. It doesn't seem like the situation would be different for apps that replace legit ones.
Sadly a large part of the iPhone user base will click ACCEPT to anything that pops up, without even reading it. It's what America has become... we don't read, then we complain we've been scammed.
If you are a developer, you should know that you can easily embed the provisioning profile right into the app bundle. Just name it "embedded.mobileprovision" and put it into /Payload/.app. There is no need to install the profile separately. This works with both ad hoc and enterprise profiles. And in iOS 8, Apple has practically made the provisioning profiles invisible to the end user. Neither is there a separate prompt for its installation, nor is it visible in the settings afterwards.I've done iOS development and know that this requires a provisioning profile (separate from the app certificate) onto the device in order to install the app. This provisioning profile install requires user input, e.g. tap "Install" when prompted.
ipa bundles that have been signed with a valid enterprise distribution certificate (no matter if it's legit or stolen) and include a matching provisioning profile will install on any iOS device with one tap. It does not need to be jailbroken, nor does the user have to have any profile pre-installed.Unless your iOS device is JailBroken (not a good idea unless you're well versed in computer/network security) or you install applications that your company develops and distributes internally via an Enterprise Developer Account, you have nothing to fear.
If you are a developer, you should know that you can easily embed the provisioning profile right into the app bundle. Just name it "embedded.mobileprovision" and put it into /Payload/.app. There is no need to install the profile separately. This works with both ad hoc and enterprise profiles. And in iOS 8, Apple has practically made the provisioning profiles invisible to the end user. Neither is there a separate prompt for its installation, nor is it visible in the settings afterwards.
ipa bundles that have been signed with a valid enterprise distribution certificate (no matter if it's legit or stolen) and include a matching provisioning profile will install on any iOS device with one tap. It does not need to be jailbroken, nor does the user have to have any profile pre-installed.
It's like saying "Only install Sandboxed Apps on your Mac - warning!" - heck, I had to adjust my security settings just to install Adobe software and MS Office. This "new" feature in OS X bugs the crap outta me...they "only" want you to get your programs from THEIR online App Store...and pay Apple every cent...really??? Most hi-end software from 3rd party developers is not on the Mac App store. Even something like VLC must be downloaded from the web....and your Sandboxing "allow everything" has to be selected. Doh!
Well, IMO there are really two issues that make this dangerous: (1) The fact that any signed app bundle can replace an existing app on the device and access all its private data, and (2) that Apple has made it very easy to install apps outside of the app store using enterprise provisioning profiles. (1) is a real security flaw; Apple should only allow a bundle to replace an existing app if it was signed by the same developer. (2) is a design choice; apparently Apple doesn't want to confuse employees who install enterprise applications (keep in mind that those are not only technical people, but also administrators, managers etc.) and decided to basically hide the fact that a provisioning profile is being installed. Both are bad choices IMO.If there's a security hole- it should be patched. And if this warning helps expedite that, it's not a bad thing. No matter how big or little of an issue WE think it is.
Well, IMO there are really two issues that make this dangerous: (1) The fact that any signed app bundle can replace an existing app on the device and access all its private data, and (2) that Apple has made it very easy to install apps outside of the app store using enterprise provisioning profiles. (1) is a real security flaw; Apple should only allow a bundle to replace an existing app if it was signed by the same developer. (2) is a design choice; apparently Apple doesn't want to confuse employees who install enterprise applications (keep in mind that those are not only technical people, but also administrators, managers etc.) and decided to basically hide the fact that a provisioning profile is being installed. Both are bad choices IMO.
This summarizes the actual reality fairly well.Well, IMO there are really two issues that make this dangerous: (1) The fact that any signed app bundle can replace an existing app on the device and access all its private data, and (2) that Apple has made it very easy to install apps outside of the app store using enterprise provisioning profiles. (1) is a real security flaw; Apple should only allow a bundle to replace an existing app if it was signed by the same developer. (2) is a design choice; apparently Apple doesn't want to confuse employees who install enterprise applications (keep in mind that those are not only technical people, but also administrators, managers etc.) and decided to basically hide the fact that a provisioning profile is being installed. Both are bad choices IMO.
How can you explain this to a 45+ years old Man or Woman? or a 14 years old girl? Here's the thing, you can't and should never expect everyone to be internet smart, this is something Apple needs to address, and the whole "I'm too smart to fall for this" notion doesn't work in this scenario, it amazes me how far people are willing to go just to clear Apple's record from any responsibility, this way of thinking is exactly the reason why since the news broke till this moment Apple didn't say a word or patched the security hole, maybe you know your way around, check MR everyday or online security blogs but you can't expect everyone else to be alerted as well or wise enough to avoid this.
I rarely see true examples of irony in real life. But .gov warning us about malicious players? Cake taken, eaten and pooped.
But to the issue at hand: How does this get patched without a lot of legit players that have been using this profile/enterprise stuff not immediately having a lot of their processes broken?