4 ms·
If this is true, then it's a trivial enhancement to make that a configurable setting. 72 hours could be the default, if your security needs are higher, you coul
by SoftTalker 2y ago
If this is true, then it's a trivial enhancement to make that a configurable setting. 72 hours could be the default, if your security needs are higher, you could turn that down to 12 hours, or even less.
- itake 2y agoI agree, but it sounds like apple is choosing 72 hours to give time for the cops, because cops are more coordinated than criminals?
- xethos 2y agoI wouldn't assume this is explicitely to help LEO, but more because this is (AFAIK) the first time this is being trialed by Apple. 72 hours is a touch long, IMO (and based on some comments, it's not just me), but when your update touches millions of devices, it's also best to test thoroughly and have the first iteration be too long rather than too short. It's easy to drop the 72 hours in a future update, or tie a shorter delay to (as I believe Apple calls it) Lockdown Mode - the more important thing might be to keep the "It just works" assumption most people (myself not included) seem to have vis-a-vis Apple products. Notably, I assume it will never be user-configurable directly. Possibly through Lockdown Mode ("If enabled then shorter delay"), but I wouldn't count on Apple adding an explicit setting.
- macintux 2y agoI’m betting it’ll be configurable via MDM.
- alwillis 2y agoI’m assuming the ability to configure this will be added to Apple Configurator at some point. Any savvy user can download it for free. I used it recently to create a profile for a friend I’m working with to configure their email account. If you’re the tech person for your friends and family, Apple Configurator is quite handy: https://support.apple.com/guide/apple-configurator-mac/intro-to-apple-configurator-cadf1802aed/mac https://support.apple.com/guide/apple-configurator-mac/intro...
- threeseed 2y agoIt could just be for the user experience. There are people I know especially older who don't use their phone every day.
- eleveriven 2y agoA balance between security and giving law enforcement a reasonable window to act
- siva7 2y agoNo because 3 days is about the timeframe a phone would survive without recharging and without confusing the masses why things stopped working
- chatmasta 2y agoIf this were configurable, I would make it 30 minutes and increase it if I noticed any inconvenience. But I doubt that I would. I already have my phone in permanent do-not-disturb (so a reboot causing delayed notifications wouldn't be an issue), and it's not like I mind entering my passcode instead of FaceID every 30 minutes.
- karlgkk 2y agoI don't know where you live, but in the US it's basically understood by the courts that FaceID is not protected, but PIN is. So if your threat model includes the sort of attacker that has a phone exploit or the ability to confiscate it, you should not be using FaceID. Instead, consider using six digit PIN with auto-delete after 10 attempts. Also enable Lockdown Mode And if you use iCloud, enable Advanced Data Protection.
- chatmasta 2y agoYeah, I consider FaceID to be basically a time-limited vulnerability akin to "remember me," because unlocking is a matter of just showing your face. It's convenient and I like it, but I don't get too upset when it asks me to enter a PIN (although I am annoyed when it doesn't respond well to the "swipe up to enter passcode").
- duskwuff 2y ago30 minutes would be excessive. Keep in mind that the phone is unusable while it's rebooting, and that rebooting uses a nontrivial amount of power.
- chatmasta 2y agoRebooting takes ~7 seconds and ideally only happens when I attempt to use it. But regardless of that.... why does it take a nontrivial amount of power?
- klausa 2y agoBecause booting is relatively CPU-intensive, compared to being at idle. But iPhones do not boot in 7 seconds either — it's closer to 40. At least that's what it took on my 16 Pro Max right now when I tested it.
- threeseed 2y ago> If this is true, then it's a trivial enhancement to make that a configurable setting It could be hard-coded into the Secure Enclave so it can't be disabled if the phone is jailbroken.
- saagarjha 2y agoA sufficiently powerful jailbreak would be able to override that.
- threeseed 2y agoNot aware of anyone being able to patch the Secure Enclave code to date.
- benmmurphy 2y agothere are public exploits to patch secure enclave code for some of the checkra1n devices. pongoOS uses the blackbird exploit on some models to remove a check that disables access to user data if the SEPOS boot code determines the phone has been DFU booted by checking the hardware TRNG state. https://github.com/checkra1n/PongoOS/blob/master/src/drivers/sep/sep.c https://github.com/checkra1n/PongoOS/blob/master/src/drivers...
- eleveriven 2y agoMaking it configurable would be a logical next step
- wiredbox 2y ago[dead]