Five Hundred Posts
Believe me or not, but this is exactly the 500th post in our blog! The first one was posted in March 2009 and was about Distributed Password Recovery and GPU acceleration. At that time, we even did not do mobile or cloud forensics. Today it’s not about our achievements. I want to thank you for being with us, and share a few bits and pieces about our blog that you may find handy or at least amusing.
👉 https://blog.elcomsoft.com/2020/10/the-five-hundred-posts/
#GPU #password #passwordrecovery #tips #jailbreak
Believe me or not, but this is exactly the 500th post in our blog! The first one was posted in March 2009 and was about Distributed Password Recovery and GPU acceleration. At that time, we even did not do mobile or cloud forensics. Today it’s not about our achievements. I want to thank you for being with us, and share a few bits and pieces about our blog that you may find handy or at least amusing.
👉 https://blog.elcomsoft.com/2020/10/the-five-hundred-posts/
#GPU #password #passwordrecovery #tips #jailbreak
“Get Verification Code” Is Missing in iOS 18 and iOS 26; Here’s Where It Went🤔
If you have an Apple device running iOS 18 or iOS 26 and gone looking for the old Get Verification Code option under:
Settings → [user name] → Sign-In & Security
..you’ve probably noticed it’s no longer there. A quick search turns up forum threads, support comments, and even GitHub issues all reaching the same conclusion: Apple removed it.
Some posts go further and call it “deprecated” or “Apple’s middle finger to users of older devices.”
😊 That conclusion is wrong. The option still exists in iOS 26. It just doesn’t show up the way it used to.
We tell you how to actually get an offline code in iOS 26 and iOS 18 and why this matters.
More information at the link📎
#Tips
If you have an Apple device running iOS 18 or iOS 26 and gone looking for the old Get Verification Code option under:
Settings → [user name] → Sign-In & Security
..you’ve probably noticed it’s no longer there. A quick search turns up forum threads, support comments, and even GitHub issues all reaching the same conclusion: Apple removed it.
Some posts go further and call it “deprecated” or “Apple’s middle finger to users of older devices.”
We tell you how to actually get an offline code in iOS 26 and iOS 18 and why this matters.
More information at the link
#Tips
Please open Telegram to view this post
VIEW IN TELEGRAM
Sideloading the extraction agent: a Stolen Device Protection workaround👤
A new update to iOS Forensic Toolkit is out.
The headline feature is an alternative installation method for the extraction agent – that is, deploying it onto an iPhone while bypassing the mandatory pairing requirement.
The agent can now be delivered across the network, which removes a number of limitations that came with the usual cable-based installation. One requirement up front: the device must already be unlocked – in other words, the passcode must be known. This method does not work with a fully locked iPhone.
☺️ Why a new installation method was needed?
The reason is a feature called Stolen Device Protection (SDP), which we discussed in the previous article. It is designed for the situation where a phone ends up in someone else’s hands and that person also knows the passcode.
In this mode, certain actions require biometric authentication – the owner’s Face ID or Touch ID — with no option to confirm the operation by entering the passcode. The checks tighten when the device is away from familiar locations such as home or work, and in settings they can be enforced at all times, regardless of location.
❗️ Previously this protection could only be enabled optionally, and it was rarely encountered. Starting with iOS 26.4, that has changed: Apple turns Stolen Device Protection on automatically. As a result, examiners increasingly run into devices that simply will not allow a USB connection to a new computer.
😊 The alternative agent delivery methods solve this.
More information at the link📎
#EIFT #Tips
A new update to iOS Forensic Toolkit is out.
The headline feature is an alternative installation method for the extraction agent – that is, deploying it onto an iPhone while bypassing the mandatory pairing requirement.
The agent can now be delivered across the network, which removes a number of limitations that came with the usual cable-based installation. One requirement up front: the device must already be unlocked – in other words, the passcode must be known. This method does not work with a fully locked iPhone.
The reason is a feature called Stolen Device Protection (SDP), which we discussed in the previous article. It is designed for the situation where a phone ends up in someone else’s hands and that person also knows the passcode.
In this mode, certain actions require biometric authentication – the owner’s Face ID or Touch ID — with no option to confirm the operation by entering the passcode. The checks tighten when the device is away from familiar locations such as home or work, and in settings they can be enforced at all times, regardless of location.
More information at the link
#EIFT #Tips
Please open Telegram to view this post
VIEW IN TELEGRAM