We have created an abc.pkg installer which contains two different packages; a def.mpkg(bundle style) and a ghi.pkg(flat package). The installer supports OS version 10.5 and above. We have digitally signed the abc.pkg installer and based on Apple's documentation we simulated Gatekeeper's behavior.
The signed abc.pkg passes the spctl control:
spctl -a -v --type install abc.pkg
returns:
abc.pkg:accepted
source: Developer ID
which based on the documentation mentioned previously means that Gatekeeper will accept our package's signature, but fails the check-signature control:
./check-signature ~/path_to_the_installer/abc.pkg
returns:
(c) 2014 Apple Inc. All rights reserved.
/path_to_the_installer/abc.pkg: code object is not signed at all
NO
which means that the signature doesn't meet Gatekeeper requirements.
We have tested abc.pkg installer on a Mac OS X 10.6 and on a Mac OS X 10.10 and the installation was successful both times.
What exactly means that abc.pkg doesn't meet Gatekeeper's requirements and which are the consequences of the check-signature tool failure?
Shouldn't we see Apple's warning:
"abc.pkg" is from an unidentified developer. Are you sure you want to open it?