3 ms·
I'm just not sure how that would work, without Apple, or the Developer having the opportunity to introduce malicious code. Signature or not, known process or no
by TheZenPsycho 13y ago
I'm just not sure how that would work, without Apple, or the Developer having the opportunity to introduce malicious code. Signature or not, known process or not, there's no way I can think of to compare a clean compile of source, to the binary that you get on the app store since Apple retains a private key that is used to molest the binary in some way.
You would have to mean something else by "open its distribution process"
Or just blindly trust that Apple knows what they're doing and that it has its customer's interests bound to its own commercial interests.
- stcredzero 13y agoYou compile it and do the same things to it Apple would have.
- TheZenPsycho 13y agoRight you just need Apple's private key. That should be easy, and not compromise the integrity of the whole system at all.
- stcredzero 13y agoThis is why I mentioned the public keys. You can do the parts of the process short of the signing, then go the other way from the published binary with the public keys. Sheesh, does everyone on HN need everything spelled out for them?
- TheZenPsycho 13y agoYou're assuming the signing process is reversible?