Ah nice Vade, and that sounds pretty easy to boot.

...and thanks @ Achim for your thoughts as well.

-gt

On Apr 6, 2012, at 11:25 AM, Anton Marini wrote:

> You could maybe do something where you check the main bundle in plugin init, 
> and return nil if the bundle ID does not match your host applications bundle 
> ID. This avoids the complexity of encrypting a bundle. It also means you can 
> set up dev builds easily that work in the editor, and in your app, and no 
> where else. A #define away and building release means it works only in your 
> app.
> 
> 
> 
> On Apr 6, 2012, at 4:03 AM, Achim Breidenbach wrote:
> 
>> Hi George,
>> 
>> I never heard of that. If I read correctly between your lines, your are 
>> looking for a method to protect your custom plugin from copying and 
>> unauthorized usage. Maybe you can implement some kind of encrypted input 
>> key, that can only be fed correctly by your host application? If this input 
>> isn't filled in correctly your plugin will refuse to work. To make it hard 
>> to hack, there should be a output from the plugin where the input value 
>> should relay on, so that on every start of your plugin the key is different. 
>> With this you would have to run your plugin for some render cycles before it 
>> can determine if its in the host app or not.
>> 
>> best,
>> 
>> Achim Breidenbach
>> Boinx Software
>> 
>> 
>> On 05.04.2012, at 20:37, George Toledo wrote:
>> 
>>> 
>>> Is it possible, using the standard API, to set it up so that QC can't load 
>>> my qcplugin, but only my custom app can, eg., set up an "exclusive host" 
>>> relationship?
>>> 
>>> Thanks,
>>> gt
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Quartzcomposer-dev mailing list      ([email protected])
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/quartzcomposer-dev/achim%40boinx.com
>>> 
>>> This email sent to [email protected]
>> 
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Quartzcomposer-dev mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/quartzcomposer-dev/anton%40noiseindustries.com
>> 
>> This email sent to [email protected]
> 
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Quartzcomposer-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com
> 
> This email sent to [email protected]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to