AW: Standalone blocked by "software restriction policy"

Marty Knapp martyknapp at comcast.net
Sat Feb 25 17:54:26 EST 2012


Apple developers have access to certificates with which to sign their 
apps for distribution outside of the Mac App Store. I don't believe 
there is an additional charge (other than your yearly developer fee), 
though I've not used this yet, so don't quote me on that. You have to 
use both a "Developer ID Application Certificate" and a "Developer ID 
Installer Certificate."

That's all In know at this point. Maybe someone else can fill in the gaps.

Marty K
> I have code-signed Windows installers and executables as well, though not yet
> in a LC project. (Soon, I'll have to do it on the Mac, too. I believe
> code-signing is required to get an app in the app Store. Apple's next MacOS
> update is going to make more use of code-signing.)
>
> Code-signing may seem a PITA, but if you've ever had your personal identity
> stolen, then you'll warm up to this solution which lets you stamp your
> identity on your digital work so that others cannot alter it for their own
> purposes and pass it off as you. Imagine if your app were injected with
> malware, zipped up and then uploaded to countless sites. Yikes! Code-signing
> is a way for professionals to protect their reputations and their clients.
>
> Here's one source for code-signing certificates and tools:
> http://codesigning.ksoftware.net/ http://codesigning.ksoftware.net/
>
> All this said, I have not personally code-signed a LC project yet, so I
> cannot say for sure that it works. (In the Director world, there is much
> anger at Adobe over the fact it has not enabled code-signing of Director
> projectors.)
>
> -- Tom Bodine





More information about the use-livecode mailing list