[gmpi] Re: 3.18 Copy Protection

>>>
And how do you prevent me from writing a mini DX plugin that is also a
host that fakes your handshake, and then can load these "locked" plugs
in
any host?
<<<

You can't.  As I said, no system can be perfect. 

>>>
I mean, we *really* don't want to encourage plugs that are locked to
hosts.
<<<

But *we*, Cakewalk, require this.  Plugin vendors that we've worked with
want to protect their reputation, they don't want their DSP crown jewels
shared so easily.  They like the idea of locking their bundled plugin to
the host with which it was bundled.

>>>
Define secure?  The plugins are the thing we want to protect, so any
host-centric security is moot.  A host can be faked.
<<<

True enough.  That's why I added the other idea about all plugins
checking each other.

----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules:  Please stay on topic.  You are responsible for your own
words.  Please respect your fellow subscribers.  Please do not
redistribute anyone else's words without their permission.

Archive: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: