Meatball protected stacks :-)

[Peter Haworth]

I have submitted a QCC report for this.  It is # 10292.

Jacque, thanks for your suggestion but the properties I'm concerned about
do change so the script idea won't work.

My thoughts so far are either to encode the cprops or use global variables
instead.  Encoding them prevents a user from discovering what they are but
doesn't prevent them from deleting or changing them, thus completely
f***ing things up and causing unnecessary support headaches.  For that
reason, I'm inclined to go down the global variables path.

Pete
lcSQL Software <http://www.lcsql.com>



On Fri, Jul 6, 2012 at 6:50 PM, J. Landman Gay <jacque at hyperactivesw.com>wrote:

> On 7/6/12 6:12 PM, Richard Gaskin wrote:
>
>> Peter Haworth wrote:
>>
>>  In the meantime, there are some custom property values that I just don't
>>> want to hardcode in scripts.  I guess my only option is to encode them
>>> somehow.
>>>
>>
>> The problem with reading values from scripts is that the script property
>> can't be read from objects within a locked stack.
>>
>> If you need to encrypt data you might consider using the encrypt command
>> with data stored in a custom prop.
>>
>
> I usually use encrypted properties. But it's possible to embed secret
> things in scripts even if the stack's locked:
>
> function getSecretThing pType
>   switch pType
>   case "password"
>     return "mypass"
>     break
>   case "username"
>     return "mrEd"
>     break
>   case "keysToKingdom"
>     return "aHorse"
>     break
>   end switch
> end getSecretThing
>
> It only works if the secret things don't change though.
>
> --
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
>
>
>
>
> ______________________________**_________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>