ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

How software publishers can squash piracy

Updated on August 16, 2008
Finally a solution to entering A7HP1 D731B XU30V AL02B1 93NS9 ZS82M B290DK...
Finally a solution to entering A7HP1 D731B XU30V AL02B1 93NS9 ZS82M B290DK...
 

It never ceases to amaze me how no sooner do I rip the cello wrap from my latest box of brand new software that I've shelled out hundreds if not thousands of dollars for, that I realize that there is already a cracked version complete with keygen that I could have illegally downloaded in a matter of minutes and at no charge at all (unless you consider criminal charges).

The basic flaw with the vast majority of software authentications is that they call for the entry of a "secret" long code in order to activate the program. This long code is usually the result of a complex calculation which takes the serial number and subjects it to all sorts of hexanumerical scrambling. Hackers can crack these calculations in nanoseconds, and then incorporate them into keygens which will fool your application into thinking that it has been duly validated and is an official copy.

Even Adobe who supposedly has an impenetrable online validation system features an easy workaround. Just choose to validate not on the internet but by telephone. You will now be presented with a screen that any keygen will make short work of. So much for rock-solid validation!

There are other, more secure options, but they are almost universally so burdensome to the user that they represent an insufferable imposition. Anyone who has had to validate their copy of Windows by calling Microsoft's toll free number and going through the process of reading out endless codes to the bored-sounding operator and then typing in an even more endless code of junk into the Windows Activation boxes will testify that although steps should be taken to ensure that only full paying customers have access to software, this level of gobbledigook is patently ridiculous.

The answer is to make a very minor change to how the hexanumerical scrambling is done. All that needs to be implemented is that the serial number to validation code calculation be done on secure servers belonging to the software publisher. Each serial number would have a lookup database of a single random set of characters. The calculation is then completed by factoring in this random sequence and generating an authorization code which is not only unique to that serial number, but uncrackable by any keygen. This system would also avoid registering many different users with the same serial number as each calculation would only be allowed once.

Therefore, when the new legitimate software owner wants to activate his software, all he has to do is to hit a button which allows the software to connect to the publisher's servers, communicate its serial number, have the server calculate the proper authorization code and unlock the software. This could be done in a couple of seconds without any need for users to key in A7HP1 D731B XU30V AL02B1 93NS9 ZS82M B290DK... until his fingers fall off.

The reason why software publishers may not have wanted to embrace this concept is because they want to allow the purchasers of their software who are not connected to the internet to be able to validate their registrations, but in this day and age, how many purchasers of expensive software applications are there who also don't have at the very least dialup access to the web? This solution can ensure that only customers who have legitimately paid for their software can activate it, and put the Trojan-Horse riddled keygens and their hacker creators out of business.

 

Check out hundreds of Hal's PC Technology articles in these categories:

Comments

    0 of 8192 characters used
    Post Comment

    • profile image

      Andr3az 9 years ago

      "The answer is to make a very minor change to how the hexanumerical scrambling is done. All that needs to be implemented is that the serial number to validation code calculation be done on secure servers belonging to the software publisher. Each serial number would have a lookup database of a single random set of characters. The calculation is then completed by factoring in this random sequence and generating an authorization code which is not only unique to that serial number, but uncrackable by any keygen. This system would also avoid registering many different users with the same serial number as each calculation would only be allowed once."

      What you just described is basically used in Steam ( go check in google ). It is almost keygen free, but people have bypassed it and now you can get nonsteam games from some torrent or something.

    • profile image

      Lattyware 9 years ago

      Yeah, Genius, I'm sure.

      And how do you stop the pirates from getting the signal that it sends from the server that verifies the key to the software, and faking that?

      Nice idea. Shame you didn't think it through.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: "https://hubpages.com/privacy-policy#gdpr"

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)