3 ms·
Vetting binaries is the proper solution. Apple has never promised that the device could run your garage-built tinkercode, root kits, etc. Read the box before
by new_realist 7y ago
Vetting binaries is the proper solution. Apple has never promised that the device could run your garage-built tinkercode, root kits, etc. Read the box before you buy.
- nixpulvis 7y agoThe first Apple computer was literally tinkercode built in a garage. Just saying. Nothing saying you can't still vet binaries, or better yet, the source itself.
- scarface74 7y agoSo you inspect the source code of everything you run? Did you find the HeartBleed bug that was in open source code for over 18 months?
- nixpulvis 7y agoNo, surely I don't / didn't. That's not the point at all. Security issues will ALWAYS exist, no matter how many bots at Apple check over the submissions. But why couldn't Apple open source their automated scanning software so I could run it locally? Why couldn't they publish reports on the state of application ecosystem? Why not release lists of sponsored developers (with signatures)? A paranoid organization can still not give users root, or install access. And secure OS could in theory not install things without checking them locally. Problem solved?
- scarface74 7y agoTheir “automated scanning software” basically just checks for calls to private methods. You don’t call private methods by accident.
- nixpulvis 7y agoI think you've just helped my case.
- scarface74 7y agoNo the review process is much more than an “automated scanning process”. What was your point?