2 ms·
It doesn't have to be a huge hexadecimal code; it just needs to be as complex as the device's unlock password. After all, that's what the user, through his choi
by Someone 11y ago
It doesn't have to be a huge hexadecimal code; it just needs to be as complex as the device's unlock password. After all, that's what the user, through his choice of password, chose as the desired security level. In fact, it just _could_be_ the unlock password.
The secure enclave (https://www.mikeash.com/pyblog/friday-qa-2016-02-19-what-is-the-secure-enclave.html https://www.mikeash.com/pyblog/friday-qa-2016-02-19-what-is-...) could generate a public/private key pair, keep the private part for itself, and give up the public part when given the unlock password.
It could even generate a new key every time someone asks for one, and only accept the last one it sent out.
But yes, as I outlined, one problem with this is "no more updates for you".
A way halfway around that could be for the secure enclave to accept unsigned firmware updates, but to first destroy the device's encryption key ("sorry, no more updates for you, unless we are allowed to erase your device first")