Re:We’ll stop selling our Code Editor app for iOS soon
by SheinhardtWigCo on Tuesday May 11, 2021 @11:32AM
(#27119328)
How is this significantly different from:
1) link JavaScriptCore
2) download JavaScript code from the internet
3) provide code to JSC
4) ???
5) Profit!
Re:We’ll stop selling our Code Editor app for iOS soon
by eat_veggies on Tuesday May 11, 2021 @11:39AM
(#27119432)
I suppose the difference is that JSC can only execute javascript (an interface which is relatively self-contained and which Apple can control) and not arbitrary machine instructions?
Re:We’ll stop selling our Code Editor app for iOS soon
by egeozcan on Tuesday May 11, 2021 @11:45AM
(#27119513)
But you can't provide a JS JIT as well.
Re:We’ll stop selling our Code Editor app for iOS soon
by lacker on Tuesday May 11, 2021 @12:24PM
(#27120058)
Apple makes sure that JavaScriptCore can safely run untrusted code, but they don't apply that same level of security to their native API.
Re:We’ll stop selling our Code Editor app for iOS soon
by candiodari on Tuesday May 11, 2021 @01:55PM
(#27121255)
JIT's can be made 100% secure. Inspection by humans cannot be made secure, for a lot of different reasons. So it's just the opposite.
I've run bots that executed code from the internet and while yes, I've had to learn some lessons the hard way, you can have perfectly safe JITs.
But, it is.
1) provide a JIT compiler
2) download code from the internet
3) provide code to JIT compiler
4) ???
5) Profit!
JIT code obfuscates the inspection of the app. It therefore is a security concern.