2 ms·
There have been bugs that allowed you to do crazy things because of Safari’s JIT before (to the point they added a switch to the OS to disable it). Maybe they f
by easton 2y ago
There have been bugs that allowed you to do crazy things because of Safari’s JIT before (to the point they added a switch to the OS to disable it). Maybe they figure if Apple can’t write a safe one nobody else can either?
- JKCalhoun 2y agoI should think proper sandboxing of the rest of the OS should contain the mayhem to the process/container though. I think most of us on HN understand that "safety" is something you just have to accept is never 100%. As an example a team responsible for security can test the standard image libraries (libjpeg, etc.) using file-fuzzing to find any bugs around buffer overflows, etc. It's good they do this but we all know that this is still a statistical shot in the dark that may still leave a vector somewhere in the framework.
- admax88qqq 2y agoI am fairly confident that the JIT restriction is about preventing third party browser engines (chrome) from running on the iPhone, not about security. When Google looked like they were investing heavily in PWAs they could have become a threat to native apps
- jgruber 2y agoApple’s BrowserEngineKit allows for the use of JITs. I have a link to the docs in my article.
- jgruber 2y agoCorrect. If you enable Lockdown Mode, the JavaScript JIT compiler is disable by default in WebKit: https://support.apple.com/en-us/105120 https://support.apple.com/en-us/105120 So Apple considers its own trusted JIT a security threat surface.