Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GrapheneOS finds Bluetooth memory corruption via ARM MTE

grapheneos.social

Post reply on HN
Print view View original

51–60 of 228 posts

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#51

Post by loeg »

xvector wrote: post #36

> Pixels shipped a massive hardware security feature (MTE) they aren't enabling for the OS to save 3.125% memory/cache usage. It's silly. Heap MTE has near 0% perf overhead in async mode and is cheaper than increasingly ineffective legacy mitigations like SSP in asymmetric mode. I really want to see someone from the Pixel team justifying the decision here. I really wonder what the thought process is for someone to di…

The tradeoff isn't just memory use or performance -- it's also user-facing crashes that weren't present before. That is likely the bigger factor in deciding whether or not to enable the feature.

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#53

Post by m3drano »

evanjrowley wrote: post #45
wwwigham wrote: post #24

Stock Pixel may not ship with it on by default for end users, but anyone can enable developer options and enable Memory Tagging Extensions - either until toggled off, or for a single session if you're trying to test a specific app - if you do want the feature on.

For my Pixel 7a, I searched the Developer Options menu three times and couldn't find it. Searching for Memory Tagging Extensions in Settings says it's there. Is it hidden somewhere? Edit: Nevermind, I seen it's only for Pixel 8 phones: https://news.ycombinator.com/item?id=38125379

is for Pixel 8 and above, since those have Tensor G3, which is armv9 IIUC.

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#54

Post by luke-stanley »

jstanley wrote: post #50
talhah wrote: post #49

Earlier quoted context omitted.

Do things such as Gcam and Google Pay work? The two major things I need from my phone is good camera quality and being able to use Google Pay which is useful where I'm at.

I don't know what Gcam is, but it comes with a camera app. I've never used Google Pay so I don't know.

The Google Camera app can be made to work fairly easily. Google Pay's NFC payment will not work in a useful way because the environment signature differs.

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#56

Post by alex-robbins »

dtx1 wrote: post #37
actionfromafar wrote: post #15

Earlier quoted context omitted.

These phone cases with an integrated battery pack goes a long way towards replaceable batteries if you keep a stack of them. They probable put less strain and wear on the built-in battery too.

> They probable put less strain and wear on the built-in battery too. Nope, unless you can fore your phone to only charge to below 80% they strain the battery just as much if not more by keeping them at 100% all the time.

This is false. It's true that staying at 100% is harder on lithium ion batteries than staying at 40%. However, the wear due to charge cycles is way, way more significant. Your battery will see much less wear if you keep it at 100% for some time vs discharging and recharging it a few times between (e.g.) 40% and 80% during that same time.

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#57

Post by SushiHippie »

freedomben wrote: post #38
Sytten wrote: post #6

Earlier quoted context omitted.

Agreed but they do drop support for older pixel devices very very quickly which is kinda of PITA. At least the Pixel 8 is supposed to be supported 7 years.

Just a point of clarity, GrapheneOS has the same support window that Google does, so they're not dropping support earlier than the vendor. The reason they drop support is because the burden of supporting an EOL device is way, way higher, especially for a security-oriented OS.

Though the pixel 4 still gets updates from GrapheneOS, which didn't receive updates since October 2022 from Google.

So they support it even a bit longer than google officially does.

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#58

Post by asdp9iujaspid »

talhah wrote: post #49
jstanley wrote: post #17

Earlier quoted context omitted.

1. No, it was very easy. I used a normal USB cable and adb on the Linux command line, but the recommended method involves using Web USB in Chromium which is meant to be easier for non-technical people but I couldn't get it to work. 2. No, it is very convenient. It has a sandbox for Google Play Services, which IMO is the best of both worlds as it means you can install all the proprietary crapware apps that make modern…

Do things such as Gcam and Google Pay work? The two major things I need from my phone is good camera quality and being able to use Google Pay which is useful where I'm at.

Google Camera works fine, but is not included out-the-box

Google Pay will not work as GrapheneOS makes no attempt to masquerade as a Google-Certified device [0]

[0] https://grapheneos.org/usage#banking-apps

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#59

Post by SushiHippie »

meindnoch wrote: post #44
DEADMINCE wrote: post #41

Earlier quoted context omitted.

The Android UI allows complete customization, you can even make it like iPhone if you want.

This is satire, right?

https://www.macrumors.com/2022/08/19/copycat-ios-launcher-an...

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#60

Post by snoutie »

hackerman3309 wrote: post #52
snoutie wrote: post #5

[flagged]

[flagged]

I might have not caught that he tried to kill graphene os. Didn't he just say that he decided to not use gOS anymore because he thinks that the developer of gOS might have something against him personally?

Anyway, I don't know a single person who stopped using gOS because of the feud between these two

Gladly I might add since I have been enjoying gOS so far

Post reply on HN