• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: AppleScript feature request - encryption
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AppleScript feature request - encryption


  • Subject: Re: AppleScript feature request - encryption
  • From: has <email@hidden>
  • Date: Tue, 15 Mar 2005 19:46:10 +0000

Martin Orpen wrote:

The scripts are being bundled with an existing app and being sold at a
premium. If other people get hold of the scripts then they get the premium
product at the same price as the vanilla version.

The product has its own scripting language but requires some tasks to be
accomplished using AS. Another developer has come up with a method of
encrypting and securing the native scripts so that they can't be accessed -

Presumably the native scripts' source is encrypted for distribution and decrypted by the application at runtime. (Still crackable, of course - e.g. just find the point where the scripts are decrypted prior to use and listen into that - but more effort than not having to crack 'em at all.) If that level of security is good enough for other parts of the program, perhaps the same decryption mechanism could be used to decrypt AppleScript source data which could then be compiled and executed on the fly.



which has left the AS scripts as the only part of the product that is open
to this sort of scrutiny.

I presume I can get around this by doing something along the lines of:

<http://developer.apple.com/qa/qa2001/qa1026.html>

But it would be nice if there were an easier method :-(

If the application has access to Cocoa, NSAppleScript is a good bit simpler to use than the Carbon OSA API. Even if you did have to use the latter, if you don't need to pass complex data between application and AppleScript, taking that Apple example and building it verbatim would hardly present a challenge. Or, since it sounds like the bulk of the program is already in another language, assuming that language has C bindings perhaps it'd be more convenient just to implement some level of Apple event support in that language (this isn't as hard as it sounds if you don't mind a little C) and forgo AppleScript altogether. Perhaps you'd be best discussing your options with the other developer(s), see what they think.


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


  • Prev by Date: Re: AppleScript feature request - encryption
  • Next by Date: Re: Applescript-users Digest, Vol 2, Issue 175
  • Previous by thread: Re: AppleScript feature request - encryption
  • Next by thread: Re: AppleScript feature request - encryption
  • Index(es):
    • Date
    • Thread