Lawrence Finch wrote:
DollaDollaBillsYall wrote:
Lawrence, you pointing to that hack doesn’t justify this change, since as was mentioned multiple times, that hack doesn’t apply to people with encrypted backups.
As has been pointed out it DOES apply to encrypted backups, because if a hacker can download the encrypted backup to their computer, since there is no limit to the number of “guesses” for the passcode they can create a script to try every possible passcode, the same way passcodes are hacked in data downloaded from hacked websites.
Although true in theory, this is incredible in practice. Encryption for iOS backups use (at least) AES 128, with PBKDF2 with 10,000 rounds. Such a password would take billions of years to crack. When a website is compromised, it's almost always easier to simply compromise the data; as long as the site is competently implemented, it will use similar key strengths with password stretching, and probably even better algorithms now (it's the key case for "passkeys", of course, to abolish passwords altogether and simply use keys). Straightforward cracking of password hashes is less and less useful as people refrain from reusing passwords or using trivially weak passwords, so while breaches do still happen, it's not chiefly due to the cracking of passwords that they are a concern. Seriously -- this idea that a single, small fish in a vast pond would be worthy of such cracking effort is beyond silly, and the idea that protecting a backup by prompting for a passcode every time is justified for that reason is risible. Protecting the backup on the Mac, in the absence of on-disk encryption, is merely added protection whilst the system is booted; it doesn't really add any security, but is at best defence-in-depth, and the most charitable interpretation for the change is simply that Apple is extending a completely unnecessary protection to Windows users that Mac users enjoyed (very recently) from OS changes that enforce sandbox restrictions, albeit, as discussed, without any regard for the purpose of automated backups. This change is therefore policy, not security.
BTW, iOS 16.1.2 doesn't fix this issue, of course.