AnonTechie writes:
"Echoing a question asked on programmers.stackexchange.com - How can software be protected from piracy ?
It just seems a little hard to believe that with all of our technological advances and the billions of dollars spent on engineering the most unbelievable and mind-blowing software, we still have no other means of protecting against piracy than a "serial number/activation key." I'm sure a ton of money, maybe even billions, went into creating Windows 7 or Office and even Snow Leopard, yet I can get it for free in less than 20 minutes. Same for all of Adobe's products, which are probably the easiest. Can there exist a fool-proof and hack-proof method of protecting your software against piracy? If not realistically, could it be theoretically possible? Or no matter what mechanisms these companies deploy, can hackers always find a way around it ?"
(Score: 5, Informative) by frojack on Saturday March 22 2014, @03:19AM
Never charge so much for your software that anybody bothers to crack it. You can do like AutoCad did, and charge mercenary prices, and try to make everybody pay, or you can go a lot cheaper, and hope most people pay.
Our company has tried dongles, commercial protection etc and finally the problems just got so troublesome the powers that be decided activation key only.
Our customers know the software will call home to check for updates once a month. They can turn that off if they want. But because we do update it frequently with improvements, most don't. And when it does check it sends its serial number as part of the query.
Se we know the level of piracy. We know who those serial numbers were assigned to.
But it has never reached the level that we feel we have to do something about it. When a good customer with installs it on another machine, we aren't going to go after them. Not worth turning a good customer to someone else's customer.
(We have a continuing revenue stream from our customers, and losing that would cost us more than one or two additional licenses.
No, you are mistaken. I've always had this sig.
(Score: 3, Informative) by mcgrew on Saturday March 22 2014, @01:47PM
When a good customer with installs it on another machine, we aren't going to go after them. Not worth turning a good customer to someone else's customer.
You're a smarter businessman than Microsoft employs. How to lose customers. [cnet.com] Thanks to Microsoft and the BSA, the Ernie Ball corporation is running Linux and using very little proprietary software and nothing from Microsoft.
Look how hated the RIAA is. They're idiots, too.
mcgrewbooks.com mcgrew.info nooze.org
(Score: 2, Interesting) by Aiwendil on Saturday March 22 2014, @06:05PM
I have seen an interesting variation on this once. Pretty much the same setup but on a duplicate key it simply (on updates) popped up a simple:
"You are using a duplicate key. Do you want to:
a) Proceed [default]
b) reassign the key to this machine as primary installation
c) purchase a new key for $Y"
and acted accordingly, was nice enough, impled the extra install was a simple change of machine of installation, and allowed a small discount if you went thru the hassle (this software was mainly distributed with a printed manual and such, the discount was less then the cost of ordering the manual separatly)