Well considering the web links have been seen maybe we can be hopeful we'll be surprised. Who knows maybe they'll pull another Surface Mini. At the very least, Myerson seems to be keeping up to date with the speculation.
Maybe you wouldn't care to screw up a relationship/contract with MS just to feed lackeys, squatters and freeloaders. But many actually want to keep their jobs and businesses open. Either you haven't read the thread or simply do not understand the difference with this release and previous releases. A leak now could cost a LOT more than bandwidth for the original intended persons. or November
If those build hashes are what would give away the leaker’s identity, it’s quite stupid as the hash can be changed in a matter of seconds, the way of doing it isn’t public to this day as far as I know but it is real easy to do.
you can easily change the md5 (less than a second) yes. but the sha1-> stays. Quite interesting actually and it is public, just not popular since it serves no purpose for anyone on the up-and-up lol. Anyway, a simple hash wouldn't be enough for MS. They know all we would need to do, is rebuild the iso or add a txt file etc.etc.
If it isn't public, how do you know it's easy? How would leakers know how to do it? I'm very curious to find out how they can be changed...
I don't see it being a whole lot different than Win8.x machines. Each and every machine built goes through a process of getting a key acquired by the OEM from MS. Every single machine goes through a "send info->get info->send key->embed key" system. IF they can go through all that (yes it is automated), there is no reason to think each and every ISO couldn't be built on an individual basis. Especially builds that are intended for a very small audience. yes, bitswitcher and a few others have showed us that. I was thinking of the md5 changer lol
Heh, I doubt that anyone would want to leak anythings nowadays anyway... inb4 "If someone wants to leak threshold PM me for hash change instructions1!!!1!"
Microsoft doesn't care about leaks, just dont leak things as big as Activation Server SDK, Lmao, wtf were they thinking ? But again, Microsoft seriously sues and jails for that too ? otherwise both are dumb, the ones who leaked it and then Microsoft, they should arrest terrorist people instead (Lol ?)
Activation SDK gets sent to close partner / OEMS so they can mass produce computers / tablets so if a ISO leak gets out Microsoft will be on high alert its unreleased software its different when they release the ISO early on Technet/MSDN
I think it is beyond hashes and MD5. If not there are easy ways to get around them by using some software that can change them within few minutes. I have tried it before for educational purpose.