I've been wondering about the different authentication/anti-piracy methods employed by software developers and thought I might encourage a listing.
Copy protection is a contentious issue that has certainly inspired many a "spirited" debate in the past but I'm hoping for more dispassionate, matter of fact, responses to aid in creating a succinct and usable thread for reference.
As an addendum I'm also curious about software for which the developer has ceased to operate or has been "discontinued" by a developer still in business and whether or not the copy protection has made the software unusable when upgrading to a new machine or OS. Also, what current software has the potential to become inoperable should the current developer cease operation
Thanks.
Different authentication methods listed and explained with pros and cons.
-
- KVRian
- 621 posts since 11 Jun, 2011 from Detroit
Most use just a registration code of some kind. You buy the software, you enter in a code when you first load it up, then its tied to that computer/device and your email/user account for that company. This approach is good if you're just using 1 computer to do all your production work, and doesn't have the hassle of requiring you to purchase additional hardware or take up additional hardware slots on your computer.
The "dongle" system, where you have a USB thumb drive with authorization codes on it, is another popular method. Best known is the iLok system, which is a USB thumb drive that exists only to hold authorization codes. You purchase the software, you get an auth code, it gets downloaded to the thumb drive, and off you go. The pro of this is that you can work on multiple computers, and just plug in the thumb drive to allow you to use your software. This has the gigantic disadvantage of forcing you to use a dongle, which takes up a USB slot, as well as if the dongle is lost or damaged or ceases to function, you effectively can't work.
Cloud systems have become a popular way to do things in recent years. This typically requires another program to be downloaded and running in the background of your computer (think the Valve gaming system Steam) and to have a constant internet connection. It uses your IP (your internet "address") and your user account as a kind of auth code. this means you can be on any computer, and as long as the software, the extra program, and the computer is connected to the internet, you can use what you bought. You have to be online at all times, as well as have another program running to be able to work, though some allow offline modes in case you need to do work and are not near an internet connection.
The "dongle" system, where you have a USB thumb drive with authorization codes on it, is another popular method. Best known is the iLok system, which is a USB thumb drive that exists only to hold authorization codes. You purchase the software, you get an auth code, it gets downloaded to the thumb drive, and off you go. The pro of this is that you can work on multiple computers, and just plug in the thumb drive to allow you to use your software. This has the gigantic disadvantage of forcing you to use a dongle, which takes up a USB slot, as well as if the dongle is lost or damaged or ceases to function, you effectively can't work.
Cloud systems have become a popular way to do things in recent years. This typically requires another program to be downloaded and running in the background of your computer (think the Valve gaming system Steam) and to have a constant internet connection. It uses your IP (your internet "address") and your user account as a kind of auth code. this means you can be on any computer, and as long as the software, the extra program, and the computer is connected to the internet, you can use what you bought. You have to be online at all times, as well as have another program running to be able to work, though some allow offline modes in case you need to do work and are not near an internet connection.