The result is too long to paste here, and frankly I’ve no idea what it means: as long as it ends with "The validate action worked!" you should be fine. Stapler validate -verbose "/full/path/to/the/installer_signed.pkg" You can verify that the installer_signed.pkg has been really signed with: Of course you should substitute the "Developer ID Installer:" string with the one you’ve noted in the previous section, as well as the files paths. installer_signed.pkg is the path of the new, signed file that is going to be created by productsign. installer.pkg is the relative path (can be absolute as well) that points to the file you want to be signed. -sign is the argument that defines the Identity associated to the Apple issued certificated, which follows as a string.productsign is the utility in charge of the signing.Productsign: Wrote signed product archive to. Productsign: adding certificate "Apple Root CA" Productsign: adding certificate "Developer ID Certification Authority" Productsign: signing product with identity "Developer ID Installer: Davide Barranca (I2WD7PWGD9)" from keychain /Library/Keychains/System.keychain Productsign: using timestamp authority for signature Productsign -sign "Developer ID Installer: Davide Barranca". You can verify that the certificate has been successfully installed opening the Terminal and pasting the following command: When the process is complete, you’ll be presented with a download link for your certificate, to be imported via double click into the Keychain Access app. Create a new Certificate: when asked, select DeveloperID Installer:įollow the instruction to complete the process – you’ll be required to open the Certificate Assistant from the Keychain Access application to create a Certificate request, then upload it to the Developer Portal. Log in the Apple Developer portal portal and follow the “Certificates, Identifiers & Profiles” section. Create a DeveloperID Installer certificate app plus other assets) will follow in a later section. pkg installer caveats for slightly more complex scenarios (e.g. I assume that you are at least vaguely familiar with the topic of code signing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |