Identifying a certain Windows machine

Joe F. joef1 at mac.com
Tue Mar 30 04:06:37 EDT 2010


Hmm- that's an interesting angle- thanks for the input.

My immediate purpose is for a single user, private app. If anyone else  
gets access to it they could only have malicious use for it, so I'd  
want it to just destroy itself if possible.

On Mar 30, 2010, at 12:26 AM, Peter Alcibiades wrote:

>
> Don't bother.
>
> All they have to do is install in a VM, or even in Wine.  Then if  
> they move
> the VM, or the Wine folder, the machine ID stays the same.  So you  
> don't
> achieve anything, all you do is annoy your less sophisticated  
> customers, who
> will find someone who knows how to defeat it.  But it gets worse.
>
> The problem is, they will feel they have a legitimate need to be  
> able to
> move their install from one physical machine to another.  They will  
> feel
> that a restriction to one particular machine, as opposed to one
> installation, is not fair.  However, what you have then encouraged  
> them to
> do, installing on a VM, gives them the ability to install as many  
> copies as
> they want, wherever they want.  Its counterproductive.
>
> Then, you'll start to think, maybe there is a way I can detect and  
> ban VMs.
> And Wine.  Yes, maybe.  How will they see that?  Will inability to  
> run under
> Wine or in a VM seem to the customer like a value added feature?
> -- 
> View this message in context: http://n4.nabble.com/Identifying-a-certain-Windows-machine-tp1742751p1744691.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution




More information about the use-livecode mailing list