Samsung actually added Knox to their Android implementation a few months before iOS added Secure Enclave. I think Qualcomm had some sort of trusted execution environment around that time, too, if I recall correctly. And Google added Trusty to the AOSP two years ago. So it’s already running on Android, and has been for ages.
But I’m not convinced a TEE would be necessary for a device that doesn’t run any third-party native code. Browser tab sandboxing is already pretty robust; I haven’t heard of an escalation exploit being found in ages on any major JavaScript engine, meaning that the risk of data exfiltration or bootloader compromise are extremely remote, and would be much quicker (and less risky!) to patch via browser updates than firmware/OS updates.
The only other reason I know of that you’d need a TEE is for DRM, and I’d be willing to wager most people who would want a FirefoxOS phone would actively prefer not to have that on their device.
Samsung actually added Knox to their Android implementation a few months before iOS added Secure Enclave. I think Qualcomm had some sort of trusted execution environment around that time, too, if I recall correctly. And Google added Trusty to the AOSP two years ago. So it’s already running on Android, and has been for ages.
But I’m not convinced a TEE would be necessary for a device that doesn’t run any third-party native code. Browser tab sandboxing is already pretty robust; I haven’t heard of an escalation exploit being found in ages on any major JavaScript engine, meaning that the risk of data exfiltration or bootloader compromise are extremely remote, and would be much quicker (and less risky!) to patch via browser updates than firmware/OS updates.
The only other reason I know of that you’d need a TEE is for DRM, and I’d be willing to wager most people who would want a FirefoxOS phone would actively prefer not to have that on their device.