3 ms·
Perhaps he's just calling it "not unreasonable" from the point of view of Apple, not from some objective definition of reasonableness. Of course, Apple is not g
by ryandrake 2y ago
Perhaps he's just calling it "not unreasonable" from the point of view of Apple, not from some objective definition of reasonableness. Of course, Apple is not going to consider itself an attacker in its own security model. Very few software companies are honest/realistic enough to consider "inside threats" from their own software. So if (and only if) you are Apple, it's reasonable for you to trust Apple to use JIT safely.
Of course, as an end user, you need to consider third party apps and your operating system as potential attackers in your own threat model. So, from a user's point of view, allowing the OS vendor to do something that a third party app can't do, doesn't make much sense.
- eptcyka 2y agoAs a user, I would like to use a Firefox that is a real Firefox, not some chrome on top of a Safari instance. Similarily, I'd like to develop apps that make use of NFC without paying apple a 100$ a year. As a user, I'd like to use JIT compilers in emulators. Maybe I'd like to run a Linux VM on an iPad Pro, we know full well the chipset supports this wonderfully. As far as safety is concerned, memory safe JITs are a thing. If they're worried about secret APIs, an ACL can be enforced in many different ways. If they're worried about syscalls, apps with JITs in them can be sandboxed.