Mark O'Neill wrote:
I used to use Armadillo on the PC platform to
help protect my app from up-to-no-good users
that tried (and succeeded before Armadillo!)
to crack it.
I'm wondering if the method above would do
a similar thing to help protect apps from
cracking by:
• writing your app as normal
• when it's completed, drop it into a
new empty app as a resource
• call that new app your actual app
and distribute it
• then when users run your app, you
extract the real app from within it
to a temporary folder and run it
• when you close the app, it deletes the
temporary app
Unfortunately this approach won't keep crackers from getting a copy of
your unprotected file, since you can copy the app while it's running,
the cracker can just grab a copy of the temporary running instance and
distribute that. You would only be hiding your app from very unskilled
crackers. I did a lot of research on this a couple years ago, and though
I never found a solution for RB created apps that I was happy with, I
could share some of my findings with you off list. I would post them to
the list, but that would make the info available to crackers ; ^ ).
hth,
Brian
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
