Mac OS X 10.8 Mountain Lion and Gatekeeper

DSP, Plugin and Host development discussion.
Post Reply New Topic
RELATED
PRODUCTS

Post

Urs wrote:We've been busy otherwise, but what's the word on signing AUs/VSTs? - Just installer or also binaries?
How many apps or plug-ins even have installers on OSX? Usually it's just "drag to your applications folder". (Or is it the distributable .dmg itself that has to be signed?)
Top

Post

AdmiralQuality wrote:
Urs wrote:We've been busy otherwise, but what's the word on signing AUs/VSTs? - Just installer or also binaries?
How many apps or plug-ins even have installers on OSX? Usually it's just "drag to your applications folder". (Or is it the distributable .dmg itself that has to be signed?)
We do installers ever since creating Library/Audio/Presets/u-he/Zebra2 has required the user to have a sense for case sensitive spelling :oops:
Top

Post

Urs wrote:
AdmiralQuality wrote:
Urs wrote:We've been busy otherwise, but what's the word on signing AUs/VSTs? - Just installer or also binaries?
How many apps or plug-ins even have installers on OSX? Usually it's just "drag to your applications folder". (Or is it the distributable .dmg itself that has to be signed?)
We do installers ever since creating Library/Audio/Presets/u-he/Zebra2 has required the user to have a sense for case sensitive spelling :oops:
Ah! I have my plug-in itself create the default settings in /Library/Audio/AdmiralQuality/

But actual patch and bank files I allow to go anywhere as they're loaded explicitly from whatever location. As they should be, being data files. Still though, this concept often requires a lot of explaining to Mac people.

Q: "Where should I put the patch and bank files?"
A: "Wherever you'd like, just load them from wherever you put them."
Q" "???"

;)
Top

Post

Urs wrote:We've been busy otherwise, but what's the word on signing AUs/VSTs? - Just installer or also binaries?
Only the installer needs to be signed.

I have tested this by setting 10.8 security to "App Store only". Using Right-click -> Open (not Alt double-click as previously mentioned) it is possible to run the unsigned CamelPhat and CamelSpace installers. Both plugins work in Logic without any additional user action.

Peace,
Andy.
... space is the place ...
Top

Post

I gather that the plug-ins also have to be code-signed. can anyone confirm? Is it just audiounits / specific hosts?
Top

Post

hibrasil wrote:I gather that the plug-ins also have to be code-signed. can anyone confirm? Is it just audiounits / specific hosts?
Official mail from Apple: AUs do not yet need to be code signed, just their installers do. They will have to be code signed some time in the future though.
Top

Post

That's no good for older plugins though - will they still run if gatekeeper is turned off?
Top

Post

hmmm... this is what made me think otherwise:

http://www.trondlossius.no/articles/114 ... aby-sit-me

apparently he is testing a host which under NDA
Top

Post

aMUSEd wrote:That's no good for older plugins though - will they still run if gatekeeper is turned off?
Until Apple makes signed plugins a requirement, it is possible to bypass the Gatekeeper security to run unsigned installer packages using one of 2 methods:

a) Ctrl-click or right-click the installer package and select "Open"

b) Set the security to "Anywhere" for downloads in System Preferences -> Security

(the default is App Store + Signed by Developer)

Peace,
Andy.
... space is the place ...
Top

Post

ZenPunkHippy wrote:
aMUSEd wrote:That's no good for older plugins though - will they still run if gatekeeper is turned off?
Until Apple makes signed plugins a requirement, it is possible to bypass the Gatekeeper security to run unsigned installer packages using one of 2 methods:

a) Ctrl-click or right-click the installer package and select "Open"

b) Set the security to "Anywhere" for downloads in System Preferences -> Security

(the default is App Store + Signed by Developer)

Peace,
Andy.
I'm thinking more about stuff that is already installed but no longer being developed. Will that run? It would be useful to disable Gatekeeper completely.
Top

Post

At the moment Gatekeeper only checks installer packages - not apps that were installed prior to updating to Mountain Lion. It does not affect plugins at all.

If you were to do a clean install of ML obviously you then need to run the installers for each app / plugin so the signing is more of an issue but it can be disabled completely in Security preferences by selecting "Anywhere" for the Downloads option.

Unsigned installers work fine in this mode (or using the right-click -> open method), and so do the installed plugins e.g. CamelSpace is not signed yet but it will install and work in Logic / other hosts.

This may change in the future but that depends on how far Apple take this.

Peace,
Andy.
... space is the place ...
Top

Post

From what I tested it seems that the Gatekeeper settings only apply to files in quarantine. When removing the quarantine flag (extended attribute com.apple.quarantine) programs start normally even if "Only Mac Store" is set.

So mainly, Gatekeeper applies to downloaded files only. Plugins that are copied by an installer shouldn't be a problem.

I didn't test this too thoroughly, so there might some uncertainty.


Chris
Top

Post

Oh well is the new OS is as buggy as the new Safari 6 I won't be bothering to update it till it is stable. The scrollbar and drag selection are both broken in Safari 6.
Top

Post

Based on previous Mac 10.x updates the first patch for Mountain Lion will be available in about a months time. Agree that it's probably better to wait ...
... space is the place ...
Top

Post

aMUSEd wrote:The scrollbar and drag selection are both broken in Safari 6.
OK this is weird now they are working.
Top
Post Reply

Return to “DSP and Plugin Development”