patch

We were the first to report that iOS7 notifies users that they were using non-certified 3rd party Lightning cables in iPhones and likely iPads and iPods as well. Apple currently still allows these cables to charge and sync data with iOS devices but if Apple can detect these cables, that means they could also disable iOS 7 from using these cables in a future version of iOS.

One third party company called iPhone5mod (coincidentally, the company that made the cable used to demonstrate iOS7 warnings in the images here) says it has a way around Apple’s warnings and theoretically around detection at all…
Expand
Expanding
Close

As expected, Apple just released iOS 6.1.2 with a fix for the Exchange bug in iOS 6.1 that we previously reported. The 107mb update is available OTA and comes with build number 10B146 .We reported earlier this month that AOL had informed its corporate employees via email that it would temporarily disable the ability to manage meetings with Exchange on iOS devices running iOS 6.1. AOL confirmed it was working with Microsoft and Apple to fix the “continuous loop” bug, and many had highlighted the problem on Microsoft’s forums.

Fixes an Exchange calendar bug that could result in increased network activity and reduced battery life.

The release notes only list the Exchange issues, but ArsTechnica looked deeper to see if it also fixed the passcode unlock bug from iOS 6.1. :

We tried the convoluted unlock exploit on our own iPhone and were able to unlock the screen successfully under iOS 6.1.1, and the same process once again unlocked the phone in iOS 6.1.2. Put simply: it doesn’t look like this update fixes the passcode unlock bug, according to our testing.

A previous report from iFun, which predicted today’s release of 6.1.2, claimed enhancements to maps in Japan that Apple introduced in the recent 6.1.1 beta would reach consumers in the coming weeks as iOS 6.1.3.

Update (Feb 21st): This has been fixed according to a reader. The iTunes and App Stores use HTML on the backend so Apple can “push” updates via backend code changes:

As of this morning, the bug is gone! No update required! Looks
like the somehow they pushed the update! I can no longer change the
account in the App Store or iTunes store! This reminds me when I was
beta testing 6.0 and Apple changed the behavior of downloading updates
not requiring a password (they also allowed free apps with no password
for a short while). That didn’t need an update to change either.
They seem to have ways of fixing App Store behavior without needing to
update iOS. I’m still running 6.1 on my devices, haven’t gone to
6.1.2 yet.

Would be nice for an official answer from Apple, but so far, it’s
working correctly! Also, I see redeem and send gift are grayed out
also, at the bottom of the App Store. Same for iTunes Store.

For those unaware, iOS 6 received some beefed up Restriction settings when it was released that allowed users to select “Don’t Allow Changes” for an entire account linked to an iOS device. This option was particularly useful for schools and organizations that wanted to limit a device to a specific account and keep students and others from installing apps not approved by the institution. Without the restriction, students or employees could easily change the iTunes account linked to the iOS device. Unfortunately, as noticed by one frustrated 9to5Mac reader, it seems there are several backdoor methods of bypassing the setting…

Expand
Expanding
Close

.

As noted by ArsTechnica, Adobe just released an unscheduled patch to address two vulnerabilities that could be the source of malware attacks on both OS X and Windows. Apple has also issued a KB urging users to update. According to the advisory posted by Adobe, the attacks targeted Firefox or Safari users on Mac:

Adobe is also aware of reports that CVE-2013-0634 is being exploited in the wild in attacks delivered via malicious Flash (SWF) content hosted on websites that target Flash Player in Firefox or Safari on the Macintosh platform, as well as attacks designed to trick Windows users into opening a Microsoft Word document delivered as an email attachment which contains malicious Flash (SWF) content.

The update is available through Adobe’s website here.