News/Discussions On Windows Upcoming Products: W8.1Update-x;W365;WThreshold;Win9

I meant the hash in the build tag, on desktop

 

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...

 

Aye mattey, I see.

Anyway, I smell it coming, and it's more bad gas. Ill wait a bit longer

 

Just edit all files out, done.

 

The SHA1 would change just as fast as the MD5...

 

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

 

Because I know it, it doesn’t mean that if it isn’t public that I don’t know about it.

 

True, I guess...
Maybe if you publish it we'll get a leak

 

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.

 

So its not a good way to check if Windows ISOs have been tampered? Because I always try to check any downloaded ISOs with the MD5 and SHA1 from MSDN.

 

Not sure what point you're trying to prove, but OEMs don't get the SDK, it's for internal use only, it's kept in a high security facility in Redmond (no joke)

 

I am talking about Microsoft possibly knowing who owns the original image before it's tampered with. The hash and MD5 are good ways to find out if the ISO file has been tampered with but not knowing the original owner.

 

Now I imagine it to be much like the Alien Area 51 Hangar from Independence Day. Thank you BAV0 ; )

 

You need to login to view this posts content.

 

... but can be that the beamer was not adjusted correctly, no?

 

I figured they centered the word "Windows" and then put the logo next to it. Either that or the beamer was pointed off the screen

 

Some of you guys are not "adjusted correctly"...