Is it possible to calculate the probability a generated key will work on Battle.net?

Yes, since there is a probability for virtually everything in one form or another- Though I do not know the equation. Maybe one of the smarter members do?

The idea is to get Value1 to match Value2. Both are DWORDs, so the probability is 1 in 2^32, or ~4.29 billion. Effective, no? :)

Assuming you generated it from the public algorithm, there is a probability somewhere on the internet, search for the generating algorithm and it should turn up.

[edit] iirc, it was very low, <1%

The best way of generating keys that I am aware of gives you a 0.1% probability of success.

[quote author=Adron link=board=17;threadid=2434;start=0#msg19011 date=1061732500]
The best way of generating keys that I am aware of gives you a 0.1% probability of success.
[/quote]

That sounds right..

[quote author=iago link=board=17;threadid=2434;start=0#msg19017 date=1061734740]
[quote author=Adron link=board=17;threadid=2434;start=0#msg19011 date=1061732500]
The best way of generating keys that I am aware of gives you a 0.1% probability of success.
[/quote]

That sounds right..
[/quote]

I agree with those guys... probably about 0.1%. You'd have to spend a lot of time to do that... If you were bored you could use Yoni's Google Calculator to figure it out :P

!~!HaZaRD!~!

Well, assuming there's no pattern that you can find, I'd say the probability is exactly 0.1% ;)

Edit: My statements in this thread are valid for SC/BW keys, because those are the ones I've generated.

Would jsut using a code such as rand(1000000000000, 5000000000000)

work or do you have ot have it add and substract numbers and stuff along with that? Whats the best method to do it (make a generator)

With starcraft keys, you could generate keys starting at 1000000000000 and incrementing up, then testing to see if they're valid for install, then testing on battle.net.

Of course, between the IP bans for invalid keys and the time used to generate all the keys, it would probably take you around 6 months to generate one usable key, and then there is a high probability that it is already in use.

So, in other words, forget it, you won't be able to do it.

Because I was curious, I did something with the public DecodeCDKey function out there, hoping I could find a pattern somehow to actual working CDkeys on Battle.net [never tried to figure anything out]. I ran a "bruteforce" like program starting at 0000000000000 up to 3999999999999. If the number passed the function, it'd output it to a file. You can find my results at http://darknet.darktech.org/test/keys.txt - 39MB file, I did stop it after a while, it tended to make my computer run just a bit slow. ;)

It would probably do you more good to just study the code... It's not all that hard to look at it and understand how a cd key is made up, and how to convert cd keys between different representations.

so i tihnk if you did a code where youget a rand number then add 2 to a digit then substract form a digit etc etc does anoyne else have any suggestions


Also how would i test the cd keys could i make a online cd key tester thorugh php :) I love php

Well, considering testing a cd key doesn't require a persistant connection to battle.net, it may actually be feasable to connect with php. Perhaps you could write a PHP extention (dll) to assist with hashing/checkrevision?

perhaps amybe there is a way a can connect through sockets...

how would i send and recieve data thorugh them does anyone else ebsides me know php?

UserLoser: Most of those keys will be invalid. They'd get past the installer, but not past Batle.net.

UnderCover: You're wasting your time. To my knowledge, no one knows the algorithm for generating valid CD keys except Blizzard, and since Battle.net IPBans you for supplying an invalid key, trying to test randomly generated ones would be a futile excersise. I'd find something better to do, if I were you.

If you're serious about a key generator, there are several "alternative" ways you can go about it.

Perhaps the easiest way would be to circumvent the firewall and access Blizzard's internal corporate network (not hard, as they use outlook). From there, located their SCCS and download the Battle.net source code.

You could also kidnap one of the Battle.net programmer's daughters and ransom her for the cd-key algorithm.

The most fun way (IMO), is to go Mission Impossible-style into their headquarters and download the noc list...err...the Battle.net code.

You could get a large sum of money and pay off an employee to get it.

You could look for unchecked SQL in the Battle.net daemon by sending crafted packets.

You could take over a Cisco immediately upstream from their servers by ping flooding it and cracking the password files, and then redirect traffic until they give you the algorithm.

Those, my friends, are the only plausible solutions, according to the mathematical probability of finding a CD-key that works on Battle.net and isn't in use.

Yes I know that Arta, I really just did that for fun and curiousity and see some the results of it. I really don't need any more keys, I have plenty of working cdkeys :)

Is there an algorithm for testing DiabloII cdkeys (doesn't need to work on battle.net)? I've written a crappy app to run off of onlyer's cdkey changer to test them. It would test only about 30/s and took five minutes to find one key, that of course never worked on battle.net. I guess he used one of the MPQ functions to check it though, does anyone know how to go about this in VB?

I'm pretty sure a checkbyte will fall out when decoding a d2 cd key yes.

[quote author=drivehappy link=board=17;threadid=2434;start=15#msg19318 date=1062012165]
Is there an algorithm for testing DiabloII cdkeys (doesn't need to work on battle.net)? I've written a crappy app to run off of onlyer's cdkey changer to test them. It would test only about 30/s and took five minutes to find one key, that of course never worked on battle.net. I guess he used one of the MPQ functions to check it though, does anyone know how to go about this in VB?
[/quote]
His program probably passes iscript/vscript to install.exe that calls the EncryptKey and EncryptFile predefined functions.

My SCKeySet program also uses these functions, though it dispenses with the iscript/vscript overhead.

0000000000003 works. :)

[quote author=UserLoser link=board=17;threadid=2434;start=15#msg19356 date=1062031217]
0000000000003 works. :)
[/quote]

[code]ProductID = 0
Value1 = 2353113
Value2 = 501[/code]

I don't think there are any valid products using a ProductID of zero...