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

121–130 of 228 posts

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#121

Post by AnarchismIsCool »

pjmlp wrote: post #69

I can hardly wait until mainstream hardware catches up to Solaris SPARC in 2015, or previous memory tagged architectures, to finally tame all those memory corruption issues, only written by bad skilled developers.

I'm aware people may downvote the hell out of this, but if they do they're the ones writing the bugs: it's not "bad skilled developers" it's everyone. Memory corruption is basically a language feature of C/C++.

It's best to not perpetuate the belief that it's dumb people because very few people think they're dumb and I've seen some absolutely amazing coders write some hilarious memory bugs. It just comes with the territory of those languages. It's not "if" it's "when".

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#122

Post by pjmlp »

AnarchismIsCool wrote: post #121
pjmlp wrote: post #69

I can hardly wait until mainstream hardware catches up to Solaris SPARC in 2015, or previous memory tagged architectures, to finally tame all those memory corruption issues, only written by bad skilled developers.

I'm aware people may downvote the hell out of this, but if they do they're the ones writing the bugs: it's not "bad skilled developers" it's everyone. Memory corruption is basically a language feature of C/C++. It's best to not perpetuate the belief that it's dumb people because very few people think they're dumb and I've seen some absolutely amazing coders write some hilarious memory bugs. It just comes with the ter…

My favourite quote.

"A consequence of this principle is that every occurrence of every subscript of every subscripted variable was on every occasion checked at run time against both the upper and the lower declared bounds of the array. Many years later we asked our customers whether they wished us to provide an option to switch off these checks in the interests of efficiency on production runs. Unanimously, they urged us not to--they already knew how frequently subscript errors occur on production runs where failure to detect them could be disastrous. I note with fear and horror that even in 1980 language designers and users have not learned this lesson. In any respectable branch of engineering, failure to observe such elementary precautions would have long been against the law."

-- C.A.R Hoare's "The 1980 ACM Turing Award Lecture"

After 50 years of the Morris worm, only C Machines can fix the non existence of the mythical high skilled developer, and as Hoare predicted it is finally becoming a liability not to care about security.

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#123

Post by moose44 »

kaba0 wrote: post #102
moose44 wrote: post #66

Earlier quoted context omitted.

This is also satire, right?

I’m not the parent commenter, but not really. Daniel Micay himself said that iphones are one of the best choices from a security perspective, GrapheneOS closing the gap. The reason is the close working together of hardware and software, which is very seldom done in case of Android devices - pixels being the sole exception that care about it, that’s why they are the only supported device. Not much point in buying some…

The problem with the iOS ecosystem is that it's not safe from manufacturer spying? This is the much larger issue than 3rd parties. Does lockdown mode prevent this?

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#124

Post by steveklabnik »

tommiegannert wrote: post #120
steveklabnik wrote: post #88

Earlier quoted context omitted.

> It ended up requiring a lot of RefCell (pointers to heap) Just so you know, RefCell does not inherently point to the heap. If you put a Box or something inside, sure, but on its own, it doesn't allocate.

Ah, thanks, I changed it to a Box. I confused the two, since I had to use them in conjunction.

It's all good. For what it's worth, I agree with you generally that a lot of the C code I see is like, "differently shaped" than the Rust, so it's not super simple to port directly over.

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#126

Post by [deleted] »

fddrdplktrew wrote: post #79
snoutie wrote: post #60

Earlier quoted context omitted.

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

I never installed it because of who the founder is... but maybe I'm wrong and it takes someone like this to start such a project.

[deleted]

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#128

Post by strcat »

fddrdplktrew wrote: post #79
snoutie wrote: post #60

Earlier quoted context omitted.

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

I never installed it because of who the founder is... but maybe I'm wrong and it takes someone like this to start such a project.

[flagged]

Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE

#130

Post by strcat »

mewse-hn wrote: post #99
snoutie wrote: post #60

Earlier quoted context omitted.

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

Anyway, I don't know a single person who stopped using gOS because of the feud between these two I'm looking into leaving the iOS ecosystem because the new devices are forcing faceID, and Rossman's experience with Graphene has made me very, very wary of buying into it.

[flagged]
Post reply on HN