iOS 6.1.2 Releasing Early Next Week To Fix Exchange And Lock Screen Passcode Bugs
Soon after the release of iOS 6.1, it came to the attention of the tech world that a major security flaw allowed basically anybody with a spare couple of moments to slip through the passcode system and access a device’s confidential, and supposedly secure data. The release of iOS 6.1.1 a couple of days back, which fixed lingering cellular and battery issues with the iPhone 4S, is also susceptible, and an urgent update is required on all fronts to sort this mess out. According to iFun, a German blog which accurately pinpointed the aforementioned 6.1.1 release, reckons that will likely be “early next week”, meaning those conscious as to the security of their iPhone will only have to wait a couple more days.
Whenever Apple releases a new software update, users are quickly on hand to scrutinize it from every possible angle. Yet while some issues – even the larger scale ones such as the Apple Maps fiasco with iOS 6.0 back in September – can be managed, when it comes to security and privacy, users are somewhat less inclined to forgive. A user with a little nous discovered the significant security hole on Wednesday, and what’s even more striking than the fact the flaw is possible, is just how easy an ordinary user could heed the techniques outlined to wheedle their way into anybody’s device.
The Cupertino company has often prided itself on its high level of security and seamlessness in operation of its software product, so it was always likely an impromptu update would be just around the corner. It is unknown, at this stage, whether the untethered evasi0n jailbreak would will also be patched, but from Apple’s anti-jailbreak point of view, it is more than likely the the fruit company will abruptly end to the party, but it is yet to be confirmed when the day of release comes for iOS 6.1.2.
The company has already acknowledged the Exchange problem and is said to be working around the clock to prepare a suitable fix, so hopefully, this issue can be put in the past sooner rather than later.
Source : blancer[dot]com
0 comments:
Post a Comment