I won't as I created this script just for showing how can you activate MAK key in retail version without replacing tokens.dat ........ I am not intense to cause any economical loss for that company ..... so I am not going to change the key in my script ........ btw I have a mention that I have even got more MAKs then you have shown in your list ........ however I wouldn't release them as that violate this sub-forum rule ........
Actually I am working on a keygen that can generate offline validated key based on pidgenx.dll ........ but I am not going to release it in public as it could cause me into some troubles ........ I will give you the executable once I have finished it ........
hmmmm then why don't u edit the .bat file on your own? it is pretty easy to do so on your own :\ btw I am still waiting for the activation number underflowed again (actually I am not sure it is underflowed or not lol) ......... as last time when we check the remaining activation of the key ..... it was 0 and it has suddenly changed to 3000+ again in these 2 days ......
I believe with MAK keys, the company who owns the license must request more activations and if Microsoft finds no foul play, they will up the number of activations. Whether it costs the company/organization more money and by how much I dunno. I am interested in that MAK keygenerator (especially since I have been reading about the chinese that broke the ellipse algorithm to generate keys). I was under the impression that there are several hundred quintillion (if not more) MAK keys that can be generated and only a very small percentage will successfully activate on MS servers. I would love to see your findings! I also have an unlimited MAK key if you need that for your investigation.
Exactly, that is what I meant when I said only a very small percentage will successfully activate. Essentially they create a new one when the companies purchase the volume license. Its the same thing that happens with the product key cards.
actually some of the germany / russian has made the keygen to brute forcing the private key of the ECC algorithm for Windows XP, 2k3 and Vista, but the problem is that the struct has changed a little bit for Office 2010 such that the bit offset for verification has been changed ...... I will release an updated version of my validation tool to help you investigating the MAK keys (can show you the base24 encoded number directly) ........ btw please notice that the key that used in this script has been blocked by MS activation server now