Re: AppleScript feature request - encryption
Re: AppleScript feature request - encryption
- Subject: Re: AppleScript feature request - encryption
- From: has <email@hidden>
- Date: Tue, 15 Mar 2005 19:16:29 +0000
Martin Orpen wrote:
I'm not after the *ultimate security solution*. But, rather than creating a
text file containing a bunch of AppleEvents in text format, surely it would
be fairly easy to dump the run-only files down another level so that we end
up with encrypted or binary data that cannot be interpreted without calling
on AppleScript's API?
It's already binary data (assuming you remember to use the right
build style). Variable names are retained because dynamic languages
require them at runtime, and strings are visible because, well,
that's how strings are. AppleScript doesn't encrypt the bytecode
because code security isn't a big motivating factor in its design
(low code security is the least of the language's problems anyway).
If AppleScript bytcode isn't "secure" [i.e. obscure] enough for your
needs then you're using the wrong tool for the job. The obvious
answer would be to use another language that meets those needs
better. (Maybe not the most convenient solution if you have to learn
a new language first, but certainly the most logical one.)
Personally, I wouldn't distribute sensitive code in any interpreted
language: once the development version was complete I'd port it to a
compiled language (either by hand or perhaps by writing it in Python
then using Pyrex to cross-compile it to C) and build my release
version from that.
HTH
has
--
http://freespace.virgin.net/hamish.sanderson/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden