<groan> ;-) Bob
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
