4 ms·
How is ish on iOS circumventing it?
by fxj 6y ago
How is ish on iOS circumventing it?
- londons_explore 6y agoit interprets x86, and therefore loses a lot of performance. For just running a few bash scripts, it really doesn't matter tho.
- yoz-y 6y agoThis, plus the App Store version does not come with apk package manager so in theory all executable code is there. Also they are on a kind of thin ice and already almost have been kicked out: https://ish.app/blog/app-store-removal https://ish.app/blog/app-store-removal
- lxgr 6y agoBy the way, UserLAnd [1] does something very similar on Android (and is accordingly not affected by these changes). [1] https://github.com/CypherpunkArmory/UserLAnd https://github.com/CypherpunkArmory/UserLAnd
- bitwize 6y agoFunny, all the binaries in my UserLAnd are aarch64, not x86. I'm not sure how they do it -- faking syscalls? -- but recently, changes in Android filesystem access policies made it impossible to move files between UserLAnd and the outside Android environment.
- lxgr 6y agoSorry, my comment was a bit misleading – it doesn't seem to use emulation, only syscall translation of some kind. iSH does both. For that matter, I'm actually not aware why UserLAnd's approach is compliant with the minimum API level required for the Play store but Termux isn't. I always thought the point of contention was exec()'ing executables not delivered through the store, which both of them can clearly do. Update: It seems like UserLAnd just hasn't been updated in a while, and the API level requirement is apparently not enforced for existing apps in the store.