Trying to make economic sense of open sourcing livecode

Peter M. Brigham pmbrig at gmail.com
Sat Feb 2 16:04:27 EST 2013


On Feb 2, 2013, at 3:43 PM, J. Landman Gay wrote:

> On 2/2/13 2:07 PM, Dr. Hawkins wrote:
> 
>> Then again, it might be possible to ship a non-GPL stack that was
>> password protected that would be run by the GPL or non-GPL engine,
>> although it might be impossible to handle the decryption in a way that
>> doesn't make available a key that gives effective access to the
>> source--the engine is going to need the key, and if the engine is GPL,
>> it's trivial to put a single line in to print the key on receipt . . .
> 
> RR has said that no password protection will be available in the GPL engine, and it won't be able to open protected stacks.

I assume the "password protected" refers to the kind of password protection that hides scripts and encrypts the file on the hard drive. Does this also exclude the kind of roll-your-own password protection involved in scripting an "ask password" routine on openstack (I know that this is actually not much protection except from casual hacking attempts)? Will the GPL engine continue to have an "ask password" command, or will this be taken out?

-- Peter

Peter M. Brigham
pmbrig at gmail.com
http://home.comcast.net/~pmbrig





More information about the use-livecode mailing list