How WinXP generates Activation Serials?

[JMI]

tAz:

I don't mind criticism, constructive or otherwise. The initial point of the question was the location of the MSKey4in1.exe which was both "located" and "attached" to babar0ga's post. The additional items were ones that I had found searching, and therefore knew were available with simple searching.

There is a "Magic Jelly Bean" site and I found many locations for the "Keyfinder v1.41," including the developers own site. The "RockXP 3.0" file was also easy to find in multiple places for free. The only one which seemed more problematical was the "Windows XP .NET 2003 Key Changer." I reported that it could be found under the name of "Windows XP / 2003 Product Key Viewer / Generator / Changer." I "knew" these things because I had just finished searching for them myself.

Now some constructive criticism back. Just how lazy do you want to be? In each instance I gave you the "specific" identification of the file for your search engine which I knew you could use to actually find them with little or no effort, by simply copying and pasting them into YOUR search engine.

Should I have saved you even that very minimal effort by attaching them here so you wouldn't have to make ANY effort on your own? I don't think that is actually helpful. With the proper search criteria, all these files are all over the net.

I didn't bother downloading the "Windows XP / 2003 Product Key Viewer / Generator / Changer" file, because I didn't feel like using edonkey or share connection and didn't want to deal with the crack site B.S., but again I knew anyone would get multiple hits for download of that target using the title I posted.

I did not simply say: "There are other programs out there you can find if you search." I am not "treating" you like children. I am treating you like people who can learn how to do these things for themselves, given a little guidance. I gave more than "a little guidance."

Although it is always easier if someone just gives you the answer, it actually teaches you very little. Real learning requires learing how to think for one's self and how to find answers. Teaching how to do that is much more helpful in the long run.

Do with the information as you will.

Regards,

i don't want to make this long, but i think we both understand each other.

although what you said about learning how to find things for yourself is important in the long run, sometimes, it's still good to share something even though others can find it with google's "i'm feeling lucky" instead of letting them search all over again, and search for it all over again.

sometimes, making them search is good, but other times, sharing the information without any catches is good specially for information sharing.

thanks for your time.

mmmhh Well as this topic started about WinXP and it's keys, I hope this post isn't out of place.

The Keygen authors' readme was indeed very intertesting . I did notice that he place VLK limits (for the 640 series which of course IS VLK) between 500 and 600.

I did some checking at work and none of the VLK keys (purchased as recently as last week) are within that range. Mine ( from 3 weeks ago) is around 800000(X) ( not including the last number (X) which I'm assuming is some sort of chcksum) . I wonder what's going to happen to all those "invalid" but legit purchased keys when SP2 arrives ? After reading that SP2 will be more of WINXP SE and it will "break" lots of app's currently out there, I think I'm going to stay away from SP2 for atleast a couple of months after it's release. I don't feel like being a guineapig.


just my 2c

Cheers

Star Buck

Star Buck:

There nothing to worry about for the range of VLK. the author might have ramdomly use 500 to 600 to ease the computation to get a key within that range..

Anyway, at least he left the range setting available for all to input their own range..

I've the same though as Satyric0n & rest that the explaination doc is incomplete intentionally.

Seems like someone has managed to find the exact algorithm M$ use for all it product. If it was, such a powerful tool can spell disaster for M$

JMI: BTW, It's a taboo to discuss RE/cracking M$ products here?

[JMI]

Nope, but they do have the largest force of net police looking for things related to their software.

Regards,

If that's the case, did anyone try disassemble the KG into readable code snip here?? or is it not possible?

One thing interesting is that the basic algorithm is the same for the 4 products and the programmer must have managed to find the private key that hash the required product id.. as explained by the text

Maybe just able to lcoate the 4 private key used and the basic algorithm in the code will assist in 'improvement' to the KG..

imho is cracking the cracker if you can't crack the original, quite poor.