Since the 2.0.1 update which was to stop the lock screen for passwords larger
than the 4 digit passcode (simple passcode), I have started experiencing this
problem.
What steps will reproduce the problem?
1. Cold boot or reboot (not respiring) the device. If you power off (or the
device powers off) at the first boot lock screen, the lock screen is no longer
displayed.
What is the expected output? What do you see instead?
This would be fine, except this does not give the OS the correct decryption
key. As a result access to encrypted information may fail. For myself, I have
found myself with a corrupt mail index (existing messages become "ghost
messages" with 12/31/00 or similar date) and applications that require location
services to access encrypted data (location in pictures such as "Pixelpipe")
just crash on startup on boots that the first boot lock screen has been
bypassed by power off of first lock screen.
This mobile substrate add on should be preserving the lock screen on iOS 4.x
devices when the passcode is set until the passcode has been entered once.
Re-springing continues to bypass the lock screen so to resolve encrypted access
issues, a reboot/cold boot are required. Perhaps code should be added to check
if encrypted file access is active for user processes before bypassing the lock
screen?
What version of the product are you using? On what operating system?
Exchange Unlock 2.0.1
This is my attempt to find the correct location to report/file this issue: I'm
reporting for the application:
http://modmyi.com/cydia/package.php?id=9744
Original issue reported on code.google.com by ne1fo...@gmail.com on 22 Aug 2011 at 4:12
Original issue reported on code.google.com by
ne1fo...@gmail.comon 22 Aug 2011 at 4:12