Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
strcat
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
30 ms
·
331.
▲
by
strcat
1y ago
> It forces you to give your money to Google and rely on Google hardware These are the only reasonably secure mobile devices with proper alternate OS support. It's not GrapheneOS forcing people to use these devices if they want a de
332.
▲
by
strcat
1y ago
CalyxOS was not a hardened OS and is a much different space from GrapheneOS. It hasn't provided the 2025-06-05 or later Android security patches and updates for it have been discontinued. It's strange to recommend people use an in
333.
▲
by
strcat
1y ago
Pixels are the most secure Android devices and the only ones meeting the hardware security requirements for GrapheneOS at this time. GrapheneOS is working with a major Android OEM towards their future devices meeting these requirements. Nei
334.
▲
by
strcat
1y ago
This is a post by a user on the GrapheneOS forum not associated with the project in any way from May 2024. Their post referenced April 2024 Cellebrite capabilities rather than the July 2024 data or later where they had fully caught up to re
335.
▲
by
strcat
1y ago
MTE is not about typed memory. It's for detecting invalid memory accesses outside of an object or outside of the lifetime of the object in general. hardened_malloc is the main place GrapheneOS implements MTE for userspace. In the kerne
336.
▲
by
strcat
1y ago
The early ARM Cortex MTE support has full support for synchronous and asymmetric (synchronous on reads, asynchronous on write) modes. Asynchronous was near zero cost and asymmetric comparable to a mitigation like MTE. This has been availabl
337.
▲
by
strcat
1y ago
We have regular contact with many people at Google in that space and nearly no contact with anyone at Apple as a whole. Sometimes people we know go to work at Apple and become nearly radio silent about anything technical. It's often ex
338.
▲
by
strcat
1y ago
ARM shipped it as a standard feature of Cortex cores significantly after it was added as an ISA extension. MediaTek and Exynos provide it and Snapdragon is approaching shipping an implementation. Google set it up for usage on Pixels, and t
339.
▲
by
strcat
1y ago
I think they've likely done a great job implementing it and think it will significantly improve iPhone security. I dislike the over the top marketing resembling a technical blog post. It's as if they've deployed CHERI in prod
340.
▲
by
strcat
1y ago
> I think you have to read "widespread malware attack" in Apple lit as a term of art There's widespread exploitation of Apple devices around the world by many governments, companies, etc. Apple and Google downplay it. The
341.
▲
by
strcat
1y ago
Hijacking control flow like this is not a hard requirement of exploitation. Vulnerabilities in a specific software release are not infinite in general so that doesn't mean much.
342.
▲
by
strcat
1y ago
> Apple and Google have access to similar or more information than you do, they just don't publish it for similar reasons. If that's the case, then many of their public statements about this are extraordinarily dishonest. There
343.
▲
by
strcat
1y ago
SPARC ADI was a predecessor to ARM MTE. ARM MTE has been available and used in production for several years now. ADI is also 4 bit but with 64 byte granularity rather than 16 byte.
344.
▲
by
strcat
1y ago
ARM largely built and shipped it on their own. Cortex cores were the first real world implementation. Pushing ARM to care about it as a security feature instead of only a bug finding feature is something Apple and Google are probably respon
345.
▲
by
strcat
1y ago
The side channel fixes and new MTE instruction features are not specific to Apple. Apple's blog post has some significant misleading claims and omissions. It's marketing material, not a true technical post without massive bias. It
346.
▲
by
strcat
1y ago
Typically 14/15 since a tag is normally reserved for metadata, free data, etc. Linux kernel reserves multiple for the internal kernel usage since it was introduced upstream as more of a hardware accelerated debugging feature even thoug
347.
▲
by
strcat
1y ago
It's typically used in synchronous or asymmetric mode on Android. The asymmetric mode preserves nearly the same performance as asymmetric while only having writes remain asynchronous. It's enforced once there's a read or syst
348.
▲
by
strcat
1y ago
GrapheneOS made our own integration of MTE for hardened_malloc and has done significant work on it. It wasn't simply something we turned on. ARM designed and built the feature which was made available in Cortex cores. Google's Ten
349.
▲
by
strcat
1y ago
Neither Apple or Google truly knows how widespread attacks on their products have been despite portraying it as if they have perfect insight into it. They're claiming to know something they cannot. GrapheneOS has published leaked data
350.
▲
by
strcat
1y ago
No, but Google has significantly downgraded security from it used to be and Apple isn't sharing security patches very broadly outside their company 4 months ahead of fixing them. They don't have partners to share it with. That
351.
▲
by
strcat
1y ago
Note the post title is incorrect. See https://news.ycombinator.com/item?id=45160975 . Android patches are being delayed in general, not only for AOSP.
352.
▲
by
strcat
1y ago
X cut off the link you copied within our reply. Here's that link along with 2 alternatives other than X: https://x.com/GrapheneOS/status/1964754118653952027 https://bsky.app/profile/graph
353.
▲
by
strcat
1y ago
Note the post title is incorrect. See https://news.ycombinator.com/item?id=45160975 . Android patches are being delayed in general, not only for AOSP.
354.
▲
by
strcat
1y ago
Note the post title is incorrect. See https://news.ycombinator.com/item?id=45160975 . Android patches are being delayed in general, not only for AOSP.
355.
▲
by
strcat
1y ago
Note the post title is incorrect. See https://news.ycombinator.com/item?id=45160975 . Android patches are being delayed in general, not only for AOSP.
356.
▲
by
strcat
1y ago
That's about the monthly and quarterly releases of Android, not the Android security patches. The post title is misinterpreting what's wrong. There is a lot wrong but that's not it. The baseline Android security patches are b
357.
▲
by
strcat
1y ago
Security patches aren't being delayed for AOSP specifically but rather Android as a whole including the stock Pixel OS. The title is misinterpreting our reply. We didn't say they're delaying patches to AOSP specifically. Stoc
358.
▲
by
strcat
1y ago
This is an official response from GrapheneOS: The title of this post linking our reply is inaccurate and is not what we said ("Delayed Security Patches for AOSP"). It should really be changed from "for AOSP" to "for
359.
▲
by
strcat
1y ago
The article contains libelous claims without substantiating them or providing evidence. It links to harassment content on YouTube doing the same. Both the article and those videos blatantly fabricate many things including parts which are se
360.
▲
by
strcat
1y ago
Posted a reply at https://news.ycombinator.com/item?id=44780766 . > remembering the sequences of past events The post is presenting fabricated stories directly from Kiwi Farms. I know what has happened and have a lot of i
More ›