3 ms·
I have some questions about how access to Secure Enclave, and in particular hardware keys, would work in a sideloaded app. It would be tremendously helpful if
by legutierr 5y ago
I have some questions about how access to Secure Enclave, and in particular hardware keys, would work in a sideloaded app. It would be tremendously helpful if someone knowledgeable here might be able to explain!
Wouldn't sideloading make it possible for one sideloaded app to somehow impersonate another sideloaded app, and thereby trick the PKA/SKP into signing a message with a private key that the imposter shouldn't have access to? And might we even see vulnerabilities whereby a slideloaded app could impersonate an app downloaded from the app store?
If there is no way to securely distinguish between two sideloaded apps, such that one app could impersonate another in getting access to OS- or hardware-level cryptographic services, then that could be a real problem, no? And if you have downloaded an app from a third-party app store, what is stopping that app from somehow getting access to OS resources that it could to use to impersonate another app?
Does anyone know how this issue is dealt with in MacOS?
- dannyw 5y agoA sideloaded app cannot impersonate another app for the same reason that it won't be signed with the same developer keys during compilation.
- legutierr 5y agoOK, so the OS has a way to verify the public key and the signature of the app executable, before the Secure Enclave responds to any request? Makes sense.