I wish that Bob65536's app was never posted publicly because of things like this. People will believe that it's a legit keygen, but it's not because the "secret" parameter isn't known so none of the keys are actually valid. An online check would instantly flag the key as non-genuine too. If the program WZor's posted screenshots of is released then many will blame him for ruining key leaking because he would of just made it easier for people to post fake keys. And then how would anyone know which keys are fake and which are real?
MDL should create a key validator, where the key entered is tested against the known secret IDs. The secret value database would have to be something like a antivirus signature db, easily updatable but tamper-proof. Once the MDL community proves a leaked key as being real, it is added along with the secret id to the db. So you could at least filter out fake keys for the editions we already know about...
As leaked keys are not allowed/supported here, this would be the problem of web sites, that deal with this kind of topic . Also leaked MAKs or Retail Keys have a very short lifespan before being blacklisted. So at least it's more a theoretical problem so far.
If the application gets posted then we could just look at how it's generating the secret parameter. Based off of that we might be able to check for fakes. Generated retail keys don't work anyway, so that's not something we've got to worry about. It's GLVK and OEM:SLP (Server 2012 R2) that we could have a problem with.
I don't think people understand the difference between a keygen and an activator. MS has legit keys in their database and provides valid activation responses if the hardware info matches. If not, then there's phone activation, but it also only works with valid keys from their database and will get blocked if too many people use it. It's not like those old games where all you needed was a correct key and you could play the game. Even in WZT's screenshot he installs and activates a gVLK, not a retail key. People are completely misunderstanding his keygen and what it's capable of.
That plus WZor doesn't say that it's obviously Bob65536's code and that's been posted here since 2012. All that's been added is an OS selection dropdown menu which looks to generate a handful of keys with random data entered for you. Bob65536 didn't call his app a keygen and the the average person probably didn't know how to use it. With WZor's version, however, he's called it a keygen and it automatically generates the keys. That to me says that he's desperate for the attention by claiming to have a working "keygen". A real keygen would generate retail keys and pass online checks. If he claims it can do that but doesn't release the app then he's a liar.
Indeed. A key unlocks something. simply being able to create keys that pass a cursory check is akin to creating play-dough keys. It may have the right shape, but if it doesn't unlock the door, it's not a real key.
There's no maybe about it though. It won't activate retail or OEM DM, so he probably won't release it. The only keys that will work are GLVK and OEM SLP (Server 2012), but neither of them will pass validation. Yes the system may say "Activated", but it won't remain it long term due to built in WAT. Anyone to think otherwise would be foolish.
Any idea if this publication is just an update package or maybe a ISO in order to do a clean installation of "Windows 8.1 Update 1"?
For existing 8.1 users I'd guess it will be Windows Update download and reboot. For 8.0 to 8.1 upgrade path I'd gather that they'll update their store esd download versions with the new compile version.
I understand, then one way to do a clean installation of Windows 8.1 Update1, can be creating manually an ISO, based on a Windows 8.1 RTM and add the update package (Update1) or maybe also adding other necessary updates? It would be correct this way or is there a better way?
As I understand, all parameters needed to generate keys are already known except the "secret" one and if somebody knew that "secret" parameter he could generate valid keys. WZor almost always is first then it comes to leaks, and he gets his hands on genuine ISOS even before they are uploaded to MSDN. So, my wild guess is, he has someone inside M$ and maybe this time that person has leaked "secret" parameter's info to WZor. Or maybe I just drank to much coffee. On the other hand, I don't know anything about how those keys are generated and how they pass validation, so I won't argue with you, because you're probably right. Yeah, it's a good way if you have knowledge how to do it. If you don't then Win 8.1 RTM + Windows update is painless way to achieve similar result. Or maybe this time M$ will release updated ISOS. But this is a big maybe.