![]() |
|
#16
|
|||
|
|||
|
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?
|
|
#17
|
|||
|
|||
|
Nope, but they do have the largest force of net police looking for things related to their software.
Regards,
__________________
JMI |
|
#18
|
|||
|
|||
|
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..
|
|
#19
|
|||
|
|||
|
imho is cracking the cracker if you can't crack the original, quite poor.
|
![]() |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| who knows how to generates the VENDOR_INFO string from the license key? | hanzi | General Discussion | 6 | 05-31-2008 03:43 |
| WinXP Activation Did-you-know | koncool | General Discussion | 10 | 07-10-2003 03:15 |