,
4 tweets,
1 min read
Read on Twitter
Anyone claiming "substrated handles kernel patches" has no clue what they are talking about: the reason I disagreed with jailbreakd was because it entrenched specific and _pervasive_ kernel data patches to do something as basic as code injection; Substrate doesn't do any of that.
When substrated starts, it gives itself TF_PLATFORM; after that, everything it does is "mach virtual memory sleight of hand". The exact same architecture is used by new versions of Substrate on old versions of iOS: the daemon is largely required to act as a vnode cache for hooks.
I do provide a way for jailbreaks to "slip in" kernel patches (what some people call "unrestrict"); nothing critical relies on this: these are only for sandbox backwards compatibility and to make setuid work. I do not like _any_ of these patches and never used them on my devices.
The reason jailbreaks end up getting built surrounding it is not because "it has taken over functionality the jailbreak somehow should do"; it is because "it turns out that most of the stuff that the jailbreak was doing was not only unnecessary, but actually somewhat harmful" :/.
