Re: protection scripts
Re: protection scripts
- Subject: Re: protection scripts
- From: Shane Stanley <email@hidden>
- Date: Fri, 24 May 2019 09:52:14 +1000
On 24 May 2019, at 4:35 am, Laine Lee <email@hidden> wrote:
>
> Is any of the Mavericks information about signing AppleScripts still
> pertinent in the current environment?
Yes and no. The code-signing described there will continue to satisfy
Gatekeeper under up to, and including, macOS 10.14.5, provided you already had
a developer ID (part of the paid program) at some fuzzy point around the
introduction of macOS 10.14.5. If you get a developer ID after that point, you
need to notarize instead. This involves a more rigorous code-signing, among
other things. It seems likely that the requirement for notarizing will be
across-the-board at some point, probably not far off.
If you have a developer ID and are running macOS 10.14, the free utility SD
Notary makes the process painless. See:
<https://latenightsw.com/sd-notary-notarizing-made-easy/>.
The behavoir of unsigned apps remains the same: you can use them on your own
Mac, and others can open them by control-clicking and choosing Open from the
contextual menu.
TL&DR: The current code-signing process in Script Editor (and Script Debugger)
is largely becoming obsolete.
--
Shane Stanley <email@hidden>
<www.macosxautomation.com/applescript/apps/>, <latenightsw.com>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden