Well, one way to do this is to place the stack on a server and
not at the persons location (where it can be copied).
Provide the user with a *reader* stack (see my previous post for
insight) which calls the main stack but only *caches* it
locally (so even if a third party did manage to *view* it they
would have a hard time *storing* it since it gets deleted).
Also, by storing it on a server the reader stack can query the
server to see if it is allowed to copy it for the person
requesting to view the stack. Anytime you want to expand the
viewer list you simply ask the server (where you have made
changes to a .mt script etc).
Lots of potential...
On Wednesday, June 6, 2001, at 05:18 PM, Raymond E. Griffith wrote:
> My client has a program with rather sensitive information on
> it. He would
> like it if the program installed on a computer be unable to be
> copied to
> another computer. Failing that, he would like the copied program on the
> other computer to fail to work without registration. That way
> he could know
> that another copy was around somewhere.
>
> So what is the best way to do this? I can think of putting
> files into the
> preferences file on a Mac, but what would I do with Windows? Or
> is there a
> better way?
>
> For example, I have seen the functions "queryRegistry" and
> "setRegistry",
> but I have no idea how these work or what I should do in order
> to be safe.
>
> I also note that there are such features as platform(), machine(),
> processor() and systemVersion(). A combination of these might work
> partially, but not completely.
>
> So I need some advice? Help, anyone?
>
> No, he is not paranoid. There is just a very limited market. If
> the software
> is freely able to be copied, then he loses his investment.
>
> Thanks
>
> Raymond
>
>
> 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.
>
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.
