AW: Standalone blocked by "software restriction policy"
lvhdgc7 at gmail.com
Sat Feb 25 14:49:47 CST 2012
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:
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
-- Tom Bodine
View this message in context: http://runtime-revolution.278305.n4.nabble.com/Standalone-blocked-by-software-restriction-policy-tp4408799p4421010.html
Sent from the Revolution - User mailing list archive at Nabble.com.
More information about the use-livecode