News for hackers. Stuff that matters.
Re:Today, we hacked what we'd set out to hack: the iPhone by anthk on Friday October 23, 2026 @01:44PM (#50212730)
That's why you need Rust in any image decoder. FFMPEG too.
Re:Today, we hacked what we'd set out to hack: the iPhone by NetMageSCW on Friday October 23, 2026 @02:11PM (#50213135)
Rust is not a magic security wand.
Re:Today, we hacked what we'd set out to hack: the iPhone by gejose on Friday October 23, 2026 @02:35PM (#50213457)
It might not be a magic security wand, but so many critical vulnerabilities in software trace their origins to memory unsafe code and things like "use after free".

"~70% of the vulnerabilities Microsoft assigns a CVE each year continue to be memory safety issues" - Microsoft [1]

"We adopted Rust for its security and are seeing a 1000x reduction in memory safety vulnerability density compared to Android’s C and C++ code." - Google on Android [2]

This is also worth looking: https://www.chromium.org/Home/chromium-security/memory-safet...

References: 1. https://www.microsoft.com/en-us/msrc/blog/2019/07/a-proactiv... 2. https://blog.google/security/rust-in-android-move-fast-fix-t...

Re:Today, we hacked what we'd set out to hack: the iPhone by anthk on Friday October 23, 2026 @02:42PM (#50213560)
If I were Google I'd try to rewrite Chromium in Rust. The FFMPEG folks should try porting the whole codebase to Rust too. They can always keep the legacy versions for legacy computers (my old n270 netbook can barely play 720p@30FPS anyway, and it's too slow to downsize 4k video to 720 or 480p...), so a bigger amd64 machine will always be -reallistically- needed for anything else than <=720p consumption.
Re:Today, we hacked what we'd set out to hack: the iPhone by nkjoep on Friday October 23, 2026 @03:54PM (#50214452)
What folks at Ladybird did this year. Started adopting rust for part if not all their engine.
Re:Today, we hacked what we'd set out to hack: the iPhone by notpushkin on Monday October 26, 2026 @02:43AM (#50239954)
After trying out Swift first!
Re:Today, we hacked what we'd set out to hack: the iPhone by QuantumNomad_ on Saturday October 24, 2026 @06:37AM (#50219941)
> The FFMPEG folks should try porting the whole codebase to Rust too.

They don’t seem convinced that that would be a meaningful use of time for them. (2025)

https://itsfoss.com/news/ffmpeg-swipe-at-rust/

And 6 months ago someone did a little experiment using Claude to rewrite FFmpeg in Rust. It was by the own description by the person that had the AI do it, significantly slower than FFmpeg even when incorporating assembly code from FFmpeg.

https://github.com/sharifhsn/wedeo

Maybe with further advancements it is now possible to get a better result, or soon.

But if you are going to copy their assembly code into the Rust protect how do you definitively prove that no memory unsafe operations are happening in those parts? Seems to me that either the whole thing should be safe Rust, if the point of the rewrite is memory safety.

Re:Today, we hacked what we'd set out to hack: the iPhone by GoblinSlayer on Saturday October 24, 2026 @05:38AM (#50219587)
In case of ms it's often concurrent userland-kernel transitions, and kernel doesn't control how and when they happen. Copilot is busy optimizing windows 11 and can't riir the kernel.
Re:Today, we hacked what we'd set out to hack: the iPhone by anthk on Friday October 23, 2026 @02:38PM (#50213505)
It cuts down most of the crap trying to trash your machine's RAM (virtual memory in the end, but today it's almost as if you didn't have a MMU). It's good enough.

On less powerful machines, dear Mutt+isync+msmtp users like me, please use AERC (written in Go) against these. It's slower, but far more secure than C. Also, SLRN needs a Go rewritten clone (able to point to slrn's caché) like nothing else. Comp.misc and comp.arch still are extremely valuable.

Re:Today, we hacked what we'd set out to hack: the iPhone by mr_toad on Friday October 23, 2026 @04:23PM (#50214807)
No, but it was created to mitigate these sorts of risks.
Re:Today, we hacked what we'd set out to hack: the iPhone by wat10000 on Friday October 23, 2026 @05:14PM (#50215429)
It kind of is, as is any other memory safe language.

You certainly can still write security vulnerabilities that don't involve memory safety violations, and these languages always have unsafe escape hatches that you can use to shoot yourself in the foot. But as long as you don't just sprinkle unsafe on everything, using a safer language is going to make a ton of vulnerabilities just disappear.

Looking at the issues from this past week, safe languages won't stop you from using 4 as your private key, but they would have entirely prevented the PHP vulnerability.

Re:Today, we hacked what we'd set out to hack: the iPhone by genxy on Saturday October 24, 2026 @01:42AM (#50218608)
They didn't enumerate everything you need, nor did they say Rust was a magic security wand. Cast your gas somewhere else.
Re:Today, we hacked what we'd set out to hack: the iPhone by simplesocieties on Saturday October 24, 2026 @04:56AM (#50219387)
"Seatbelts don't solve car crashes so there's no need to wear one!"
Re:Today, we hacked what we'd set out to hack: the iPhone by steve1977 on Friday October 23, 2026 @02:49PM (#50213643)
Apple has been propagating Swift for more than a decade now and at least in theory, it should be on par with Rust in terms of safety I'd say.
Re:Today, we hacked what we'd set out to hack: the iPhone by frizlab on Friday October 23, 2026 @02:55PM (#50213736)
It mostly is. Has pretty much caught up with all of rust actually (while being much more readable).
Re:Today, we hacked what we'd set out to hack: the iPhone by motoboi on Friday October 23, 2026 @04:53PM (#50215171)
They probably link libraries written in C, given the scope of the pdf and image parsing.
Re:Today, we hacked what we'd set out to hack: the iPhone by OptionX on Friday October 23, 2026 @07:50PM (#50216932)
The problem here is that pdf is over bloated with features and without strictly defined standard. Rust can't help you with that, or any language for that matter. It's akin to upgrading the security system on a house on fire.

The best solution would be ditching it completely for a simpler subset of features. But that will never happen.

Re:Today, we hacked what we'd set out to hack: the iPhone by QuantumNomad_ on Saturday October 24, 2026 @06:29AM (#50219894)
> The best solution would be ditching it completely for a simpler subset of features. But that will never happen.

Like the saying goes:

Everyone uses only 20% of the features, but it's a different 20% for different people.