Are you telling me that codesigning somehow stops my Application(s) from causing security problems, that are not of my doing? In other words, can my unsigned App cause a security breach somehow?
Is there some way my App, and the extra 6 embedded Apps, could have security breaches added by a third party? The only transfer path is by a .zip file direct from me to my Clients company mailbox.
If I am solely responsible for the coding, storage, and transmitting of my Application(s), (7 in one bundle), in what way does codesigning improve the security of the installation and running of each of the 7 Apps, for one Client?
I’ve googled, and found the pages referring to code signing Apps for outside-of-appstore distribution.
Because my App is a main App, with 6 embedded Apps, what I can’t find an answer to is…
If I archive and codesign my Mail Manager App, will the extra 6 Applications embedded in the contents, and eventually copied from the codesigned Mail Manager.app/contents to the Applications/Mail Manager folder during installation ALSO require separate code signing before being included inside the Apps contents? If so, I don’t think I’ll want to pursue codesigning. It would be too unwieldy. OR, is everything in the main App codesigned?
I don’t want to pay a fee, then find codesigning for my particular circumstances is impractical. If I were going to distribute to many Clients, I would be willing to try and go the extra mile if I had to code sign everything individually. If I had to individually code sign, I presume I’d have to individually archive each, and somehow include each archive in the main App, and open them on installation somehow. Ouch.
I like this bit…
It will solve the Gatekeeper problem, and provide some reassurance to your client (and you).
Any Guru further advice greatly appreciated.
Regards
Santa
Creating an Archive
Before creating the archive, build and run your app one more time to ensure that it’s the version you want to distribute.
To create an archive
In the Xcode project editor, select the project.
Choose Product > Archive.
The Archives organizer appears and displays the new archive.
Validating a Developer ID-Signed App
Immediately after creating the archive, validate it and fix any validation errors before continuing.
To validate a Developer ID-signed archive
In the Archives organizer, select the archive and click the Validate button.
In the dialog that appears, select “Validate a Developer ID-signed Application” as the validation method and click Next.
- In the dialog that appears, choose a team from the pop-up menu and click Choose.
Review the signing identity and entitlements, and click Validate.
Review validation issues found, if any, and click Done.
On 16 Jun 2016, at 2:30 PM, Shane Stanley <
email@hidden> wrote:
On 16 Jun 2016, at 1:07 PM, Brian Christmas <
email@hidden> wrote:
Mail Manager is written exclusively for a single Client, so I haven’t seen the need for codesigning.
That's a non sequitur. Are you saying you don't care about your client's security (or your own reputation)?
I think you're taking the wrong approach. Code signing adds minor inconveniences: you have to pay an annual fee for the privilege, and if you're unlucky, setting it up can be a bit of a pain (although it seems much, much better in Xcode 8). As far as I can see, it won't add any restrictions to what you're doing, and if it does, chances are there are things you should change anyway. You typically set it and forget it in an Xcode project, and it's just an extra export step in Script Editor. Script Debugger 6 will let you turn it on all the time for a file, so it doesn't even need to be an extra step.
It will solve the Gatekeeper problem, and provide some reassurance to your client (and you).
If code signing under Sierra still allows me to rapidly send multiple re-writes
How could it stop you?
Anyway, it's easy enough to do a trial.
--
Shane Stanley <
email@hidden>
<
www.macosxautomation.com/applescript/apps/>