iPhone_4s_db.jpg

 Improved Performance for iPhone 4S & iPad 2

Apple released ios eight.1.1 update on Monday for all units that give a boost to (or are running) ios 8. The update brings miscellaneous bug fixes and safety updates, with iphone 4S and iPad 2 – 2 gadgets that bore the brunt of the ios 8 replace relating to slowdown in efficiency – especially referred to as out in the liberate notes.

“This free up contains computer virus fixes, increased stability and efficiency improvements for iPad 2 and iphone 4s,” Apple says.

The OTA replace weighs in at forty 3.1MB for the iphone 4S, and round 64MB for iphone 6(review pictures). We strongly counsel you back up your ios device to cloud or with iTunes earlier than installing any ios replace.

iOS 8.1.1 Brings Bug Fixes; Improved Performance for iPhone 4S & iPad 2

The update additionally comprises the following security updates:

Cfne2rk
On hand for: iphone 4s and later, iPod contact (fifth generation) and later, iPad 2 and later

Impression: web page cache may not be totally cleared after leaving non-public shopping

Description: A privateness issue existed the place browsing data may stay in the cache after leaving private browsing. This difficulty used to be addressed through a metamorphosis in caching habits.

Dyld
To be had for: iphone 4s and later, iPod touch (5th era) and later, iPad 2 and later

Impact: an area user might be able to execute unsigned code

Description: A state administration issue existed in the handling of Mach-O executable records data with overlapping segments. This problem was addressed thru greater validation of section sizes.

Kernel
To be had for: iphone 4s and later, iPod touch (5th generation) and later, iPad 2 and later

Influence: A malicious utility may be able to execute arbitrary code with system privileges

Description: A validation difficulty existed in the managing of sure metadata fields of ioshareddataqueue objects. This problem used to be addressed via relocation of the metadata.

Lock screen

Available for: iphone 4s and later, iPod contact (5th technology) and later, iPad 2 and later

Impression: An attacker in possession of a tool may exceed the maximum selection of failed pass code attempts

Description: In some instances, the failed pass code attempt restrict was now not enforced. This difficulty was once addressed via further enforcement of this limit.

Lock monitor
on hand for: iphone 4s and later, iPod contact (5th generation) and later, iPad 2 and later

Impression: a person with physical get admission to the cellphone might be able to access images within the photo Library

Description: The depart a Message option in face time could have allowed viewing and sending pictures from the device. This problem was once addressed through more suitable state management.

Sandbox Profiles

On hand for: iphone 4s and later, iPod touch (5th era) and later, iPad 2 and later

Impact: A malicious software may be able to launch arbitrary binaries on a relied on tool

Description: A permissions issue existed with the debugging functionality for ios that allowed the spawning of functions on trusted units that weren’t being debugged. This was addressed through adjustments to debug server’s sandbox.

Spotlight
On hand for: iphone 4s and later, iPod contact (5th generation) and later, iPad 2 and later

Impression: unnecessary information is included as part of the preliminary connection between spotlight or Safari and the highlight tips servers

Description: The preliminary connection made with the aid of spotlight or Safari to the highlight ideas servers included a person’s approximate region sooner than a person entered a query. This difficulty used to be addressed by means of taking away this information from the initial connection and handiest sending the user’s approximate region as part of queries.

Webkit
To be had for: iphone 4s and later, iPod touch (5th era) and later, iPad 2 and later

Impression: journeying a maliciously crafted website could lead to an unexpected software termination or arbitrary code execution

Description: more than one reminiscence corruption considerations existed in webkit. These considerations were addressed via more suitable memory coping with.