Everything has changed in iOS 14, but Jailbreak is eternal [pdf]

Post by saurik » Sat, Aug 07, 2021, 10:52 PM UTC

pshc wrote: post #47

saurik wrote: post #38

The fact that Apple clearly cares a lot about software security from at least two angles--both securing the device for the user from external attackers (I know they truly care about this, even though they frankly seem to focus only on users in the west and have been known to throw people from the east under the bus without a fight: see their attempt to downplay Google Project Zero's critical discoveries a few years a…

Hello fellow poster! Line breaks would be lovely for comprehension's sake.

Post by csande17 » Sat, Aug 07, 2021, 11:07 PM UTC

techrat wrote: post #46

solarkraft wrote: post #43

Here’s a thing about jailbreaking. As a user I like my device being safe from outside attackers (NSO & co). But I definitely do not want my device to be protected against me . It’s absurd that I have to use the methods of an attacker to gain modification privileges on a device I own.

That's why Apple needs to unclench and give up its need for absolute control and just allow bootloader unlocking. Users who modify will always want to be able to modify and the only way to have that and have security as well is to allow specific ways for it to be done... not to force modders to rely on exploits.

Post by a1369209993 » Sun, Aug 08, 2021, 12:23 AM UTC

_hl_ wrote: post #36

smnrchrds wrote: post #35

Earlier quoted context omitted.

I got that part. The part I don't understand is this: what does it mean for a program to be proven correct but still not work?

It means that the correctness properties that were formally proved are not necessarily what you would intuitively understand as "correct". E.g. you can formally prove that a buggy factorial(n) always outputs (n - 1)! by incorrectly defining what you want to prove. The function behaves according to what you proved, it's just not the expected behaviour.

Post by drvdevd » Sun, Aug 08, 2021, 2:59 AM UTC

smnrchrds wrote: post #35

niea_11 wrote: post #34

Earlier quoted context omitted.

It's a comment from a correspondence between Donald E. Knuth and Peter van Emde Boas (meant as a joke I think). You can find it in this pdf at the end of the 7th page : https://staff.fnwi.uva.nl/p.vanemdeboas/knuthnote.pdf Knuth mentions it in his FAQ (at the end) : https://www-cs-faculty.stanford.edu/~knuth/faq.html

I got that part. The part I don't understand is this: what does it mean for a program to be proven correct but still not work?

Post by sildur » Sun, Aug 08, 2021, 9:43 AM UTC

csande17 wrote: post #54

techrat wrote: post #46

Earlier quoted context omitted.

That's why Apple needs to unclench and give up its need for absolute control and just allow bootloader unlocking. Users who modify will always want to be able to modify and the only way to have that and have security as well is to allow specific ways for it to be done... not to force modders to rely on exploits.

Unfortunately, it's now vital to child safety that iPhone users never be allowed to jailbreak their phones. Apple's recently-announced CSAM photo detection feature relies on Apple being sure that the real NeuralHash machine-learning model, not a fake that produces random data indistinguishable from a non-matching photo, is running on everyone's devices. So I'd say the odds of them loosening their grip here are pretty…