Thanks Jaqi and Mark. Too bad it is just as I thought it was; but since anything like that can still be hacked by someone evil enough to want and be willing to do it, why bother! I say, we just do our own hacking - where it hurts. When we stopped spanking our kids is when stuff started going wrong. When we catch someone doing something we don't want them to do, hack it off at the next joint. A hack for a hack!
Of course, when I was very young, I learned that locks didn't keep anyone out; they just kept honest people honest. If we're going to do something to protect ourselves, get offensive. If our software is hacked by anyone, it should hack them right back. Someone would probably pass a law so that we are not allowed to do that - eventually. (smile) Forgive me. I'm in a real foul mood today. Joe Wilkins Architect On Feb 28, 2012, at 12:26 PM, Mark Wieder wrote: > J. Landman Gay <jacque@...> writes: > >> Not al> If my password is "parrot", then I can either store that word and >> risk its discovery, or I can use "ask password" to encrypt it so that it's >> obscured. After encryption "parrot" becomes: =h`//q . That's the string >> you store in the stack for later comparisons. If a user enters the >> encrypted text in the password dialog it won't work, only "parrot" will. > > Since today much software is parroted, encrypting strings, passwords, > other user information, or even entire stacks can help prevent software > parrocy and data theft. > > -- > Mark Wieder > > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
