EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Hacker News·7d ago·5 min read
Pixel 11 doesn't yet meet the GrapheneOS security standards and may be skipped
TL;DR
A partial port of GrapheneOS to the Pixel 11 series has been hindered by the absence of ARM hardware memory tagging (MTE) support, a critical security feature. Google appears to have omitted this feature to reduce costs, potentially leading to the Pixel 11 being skipped for GrapheneOS support.
✦ Why It Matters
Consider evaluating the security implications of using Pixel 11 for sensitive applications today.
Key Takeaways
- Avoid purchasing Pixel 11 due to security shortcomings.
- Consider Pixel 8, 9, or 10 for better GrapheneOS support.
- Monitor upcoming Motorola devices for MTE support.
- Understand the implications of MTE on app security.
Full Summary
GrapheneOS, a security-focused Android variant, has made progress in porting to the Pixel 11 series but faces a major hurdle due to the lack of ARM hardware memory tagging (MTE). MTE enhances protection against various exploits and is integral to GrapheneOS's security architecture.
While the Pixel 8 supports MTE, the Pixel 11 does not, as Google appears to have removed this feature to cut costs. Despite some security improvements in the Pixel 11, such as post-quantum secure verified boot, the absence of MTE severely impacts its overall security.
The Pixel 11 is also criticized for being overpriced with only incremental hardware upgrades. As a result, GrapheneOS may shift its focus to upcoming Motorola devices that are expected to support MTE.