>>106537373
GrapheneOS already had this

>>106537373
I FEEL SAFE MY TITS ARE JACKED.

Did they rewrote iOS in Rust?

>>106538146
No, they invented something called guard pages and stack canaries.

Does this mean MacOS updates will take even longer?

>invented
You mean they took existing technology, renamed it, and claim it's brand new? That is what they've been doing for the past 30 years.

>>106538177
>>106538237
Forgot to reply. Here's your (You).

>>106537373
i assume this means devices are restricted to signed apps only

>>106538146
They are spending cycles (hardware enforced tagging) to mark memory locations that are accessed by the program. If your the memory accessed is labelled blue and you try to access red too, it will flag/block it.

>>106538177
APPLE INVENTED GUARD PAGES AND STACK CANARIES?!?!?!?
HOLY SHIT

otherwise it's some basic shit like this guy said, or some retarded memory tagging system that doesn't really work.

yeah but what is it

>>106538289
always has been. you can't even ship a JIT in any "app" because g*d forbid.

isn't memory tagging baked into basically every basic Cortex-A processor?
Pretty sure android's been using it for some time now. oh, sorry I mean, Apple invented memory tagging!

>>106538177
Eh.. those can't detect use-after-free.
>>106538237
The only new thing here is enforcement of correct memory access. This is an old ARM extension, which apple implemented long ago.
You're unlikely to notice any difference.

ok. I read it.
it's basically MTE, but immediately traps on tag fail instead of signalling.

>>106538475
So Apple is doing the needful and crashing cnile binaries? BASED.

>>106538518
ya... that's the high level gist. some other things in here, like constant rekeying the prng they use to pick tag values and some other shit, but ya.

>>106538354
what? i can't compile a binary and execute on the latest macOS?

>>106538538
yes? no JIT has been a rule for a long time. it gives you too many ways of messing with memory protection, plus it's still an open-ended question of the security of the actual compiler and the generated instructions it makes. hell, edge even lets you turn off JIT if you want to (for JS).
the only "JIT" you can get I believe is the JSCore engine in iOS.

>>106537373
memory errors are no longer a problem. apple just made rust obsolete.