Comments on: Registration Schemes: Serial Numbers

By: The Unix Geek

The Unix Geek — Thu, 10 Jul 2008 10:58:53 +0000

@The Joe bro
Simply create an algorithm in your application that parses the person’s first and last name and email and after running it through the algorithm check to see if the serial you gave the person is the same as the one they entered.

By: The Joe bro

The Joe bro — Wed, 09 Apr 2008 13:12:17 +0000

How would you implement this into your application?
I am confused please help. If you know of any easier ways please let me know.

By: kenneth

kenneth — Sat, 05 Apr 2008 22:46:48 +0000

@pierce: I totally agree with you. In fact, the next two parts (the first of which I just posted) describe better techniques for more expensive products.

@jonathan: I really don’t know what you dislike about this article. It describes the theory behind serial number, and simple examples you can mangle to get this type of serial numbers. You mention the arbitrariness of using MD5 followed by SHA1. But the whole point behind this type of serial is to have an arbitrary obfuscated way to generate innocent-looking serial numbers.

By: Jonathan Wight

Jonathan Wight — Fri, 04 Apr 2008 02:20:10 +0000

You really lose all credibility by even mentioning ROT13 in the context of this conversation. And the arbitrariness of MD5-ing then SHA1-ing the data just boggles my mind.

This doesn’t really encourage me to use your encryption product.

/me checks posting date, nope two days too late.

I hope parts two and three of this series merely tell your audience to go use Aquatic Prime.

By: Pierce T. Wetter III

Pierce T. Wetter III — Thu, 03 Apr 2008 23:36:58 +0000

I work for an anti-piracy company.

Unless you tamper-proof your code, you’re guaranteed a keygen.

I wouldn’t use the above scheme for a product costing > $100.

By: Generating Serial Numbers for Your App

Generating Serial Numbers for Your App — Thu, 03 Apr 2008 21:43:51 +0000

[…] Kenneth has put together a piece on serial number generation. […]