I second that. RLM should have all the tech in it to figure out VM's and spoofing. I would also say don't get overly concerned with pirating, that's just a fact of life. If you make the walls to high around your product you limit the awareness of it. Focus on legit businesses who want to pay money for your software and make it easy for them to (a) pay, (b) install/license, (c) upgrade license count.
On Wed, Oct 24, 2012 at 8:10 AM, Colin Doncaster <[email protected]>wrote: > Forgive me for asking but why wouldn't you just look at licensing a > commercial available licensing system like RLM or similar. I would say > that the amount of time spent building and maintaining your own would be > far more costly. > > Cheers > > On 2012-10-24, at 10:57 AM, Steve Booth <[email protected]> wrote: > > > Remember that it's possible to have 'virtual' Ethernet devices with > > synthetic MAC addresses. There is no guarantee that what the user sees > as > > network 'interfaces' are, in fact, actual physical hardware on the > machine. > > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Stephen > > Newbold > > Sent: Wednesday, October 24, 2012 1:30 AM > > To: [email protected]; Nuke plug-in development discussion > > Subject: Re: [Nuke-dev] Plugin Licencing > > > > Hi Pierre, > > > > Could you not just check all the mac addresses returned? If one matches > then > > you are good? If the network card is removed/changed I guess they need to > > get a new licence. > > > > Steve > > > > Pierre Jasmin wrote: > >> All OS have a way to enumerate all mac addresses (sometimes there is > >> 6, and eth0 can vary over time including if you have two ports by just > >> plugging the cable in other port) for you to strcmp The other scheme I > >> have seen is to use disk ID, this is more common for temp licenses > >> then permanent one though. > >> > >> Pierre > >> > >> On 10/23/2012 9:15 AM, Steve Booth wrote: > >>> > >>> Mike, > >>> > >>> If you're on a commercial workstation, and are not using a plug-in > >>> network adapter card, then the MAC address will be unique, although > >>> some (most?) workstations have not one, but **two** network > >>> interfaces, so there will actually be two distinct MAC addresses. If, > >>> however, you're using a plug-in card, you run the risk of crashing > >>> your software if the network hardware is upgraded. > >>> > >>> It is also possible, on Intel CPUs at least (not sure about AMD) to > >>> obtain the CPU serial number. Microsoft has the '__cpuid' macro that > >>> generates in-line, the MASM to obtain this: > >>> > >>> http://msdn.microsoft.com/en-us/library/hskdteyh%28v=vs.100%29.aspx > >>> > >>> That ties your software to a specific CPU (assuming CPU > >>> identification is enabled in the BIOS), and is much more reliable. > >>> > >>> Steve > >>> > >>> *From:* [email protected] > >>> [mailto:[email protected]] *On Behalf Of > >>> *Stephen Newbold > >>> *Sent:* Tuesday, October 23, 2012 1:03 AM > >>> *To:* Nuke plug-in development discussion > >>> *Subject:* Re: [Nuke-dev] Plugin Licencing > >>> > >>> Hi Steve, > >>> > >>> I can see how this would work when tying the plugin to a specific > >>> domain but how would you approach locking the plugin to a single > >>> machine? Use the MAC address? > >>> > >>> Steve > >>> > >>> Steve Booth wrote: > >>> > >>> Mike, > >>> > >>> How you do it depends on the OS platform you're using. Generally > >>> speaking, what I do is to get the domain name from the network stack > >>> (or just using the Win32 API under Windows), and compare it to a > >>> const string. Thus, if you're working within, say, Disney Animation, > >>> and the compositing domain is comp.disney.com, for example, just > >>> error() if the domain does not match this string. > >>> > >>> Hope that helps. > >>> > >>> Steve > >>> > > > > > > -- > > Stephen Newbold > > Compositing Lead - Film > > MPC > > 127 Wardour Street > > Soho, London, W1F 0NL > > Main - + 44 (0) 20 7434 3100 > > www.moving-picture.com > > > > _______________________________________________ > > Nuke-dev mailing list > > [email protected], http://forums.thefoundry.co.uk/ > > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > > > > _______________________________________________ > > Nuke-dev mailing list > > [email protected], http://forums.thefoundry.co.uk/ > > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > > _______________________________________________ > Nuke-dev mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev >
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
