This is an astonishing attack but it has been all over the tech news already and is explained pretty well in the securelist post. I don't have any desire to watch a video.
Technology
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
To summarise the video for you: "Yada, yada, yada... there's a blog post that covers this better, you should check it out"
For me, this kind of video has a whole, "this meeting could have been an email" vibe about it.
I can skim articles for salient details at 800 words per minute just fine. I can't stand trying to seek through a 10 minute video looking at the stills to find something of importance.
Even taking into account the Wadsworth constant and cranking it up to 2x speed it just feels like a slow way to get information across, especially when it's coupled with the standard YouTube monetisation methods.
The video doesn't go into the technical details about TriangleDB; that is left as a reference to the securelist article. Instead, the video discusses the background of the exploit, what has been done by others, what has been done since, and calls out some curiosities about the perpetrators.
I found the video to be a great summary and quite insightful.
So… can we now have decent untethered jailbreaks again?
Thank you for the video summary. That's very helpful
For those wondering: multiple security flaws that this actively exploited were fixed in iOS 16.5.1 and 17.
Stay updated. Reboot daily.
A... They found A iphone backdoor. There are others as surely as there are faults with all complicated systems.
you're talking about bugs, not backdoors. A backdoor is something intentional
The distinction between an accidental bug, and the deliberate back door with plausible deniability is minuscule.
Unless you find the smoking gun document stating the reason for the code being written this way, there's always going to be deniability, it's always going to be pointed out as a bug.
But I think it's immaterial, even if every back door starts off as a genuine bug, code is so large and complex that there's going to be back doors to be harvested. And cataloged. And kept in reserve for advanced persistent threat actors