>Is there a way to lock all the scripts of a standalone so that they can't be
>decrypted? Goal would be to have standalones that are set up to FTP specific
>files to a web site, but the user would not be able to extract the HOST,
>USER name and PASSWORD i.e. this becomes a kind of POST that doesn't require
>being handled by anything at the web site.
>
>Hinduism Today
This is what the stack password does, it locks all scripts in that
stack. If you use multiple tacks (internal or external), then you'll
need to set their passwords separately.
Also, if you use the mcEncrypt() function, you can store encrypted
copies of any user-entered passwords in your stack. Then you get the
user to input such passwords using the ask password command.
What can't be done, apparently, is lock a stack such that people
can't get at the buttons, fields etc. All you can lock are the
scripts themselves. So users with the MetaCard Starter Kit could
add, remove and modify the objects of your stack but not get at any
scripts. However, all they'd end up with is a mess and no details of
your clever code of key parameters!
Cheers
Peter
--
--------------------------------------------------------
Peter Reid
Reid-IT Limited, Loughborough, Leics., UK
Tel: +44 (0)1509 268843 Fax: +44 (0)870 052 7576
E-mail: [EMAIL PROTECTED]
Web: http://www.reidit.co.uk
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
