Topic: [WTB] Reverse engineer X-Force KeyGen for Autodesk (Read 179 times)

For some silly stupid reason that I don't understand, big companies who rely on you calling someone to get an authentication code for your software keep getting defeated by keygen that does a local mempatch then applies an algorithm based on the serial number to give you an authorization code.

Not only the keygen works but in the past, the companies used to change the algorithm but now they don't even bother to do so.

This can't be right, something is wrong. I tried to do some reverse engineering of my own, first I tried the social approach:

1. Why would a company with resources allow a keygen to work? The most logical answer I could get to is that by doing so, the company is pushing others with less means out of the market. If people can have access to their software, then these people become marketeers for life. Take that budget out from their advertisement campaign. I'm not sure how much realistic is this.

2. The second clue was in the company itself warning against the use of keygens, saying that these could be viruses that steal your data/encrypt your drive. That statement could probably win the the galactic prize for most lame excuse.

Having gotten nowhere with Google, I am looking for someone to reverse engineer the keygen. I am fairly good in reverse engineering myself, I do not need you to reverse it back to original source code with comments, API calls in Ollydb or similar would be good, just want to know what they are doing here and there.