• 0 Posts
  • 338 Comments
Joined 2 years ago
cake
Cake day: September 27th, 2023

help-circle
  • 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.







  • It’s not thinking. It’s just spicy autocomplete; having ingested most of the web, it “knows” that what follows a question about the meaning of a phrase is usually the definition and etymology of that phrase; there aren’t many examples online of anyone asking for the definition of a phrase and being told “that doesn’t exist, it’s not a real thing.” So it does some frequency analysis (actually it’s probably more correct to say that it is frequency analysis) and decides what the most likely words to come after your question are, based on everything it’s been trained on.

    But it doesn’t actually know or think anything. It just keeps giving you the next expected word until it meets its parameters.