I wonder how big this hole is to fix. I also wonder, as many have, if this was written by an Intelligence agency and, if so, if they had access to Windows' source code.
I wonder how big this hole is to fix. I also wonder, as many have, if this was written by an Intelligence agency and, if so, if they had access to Windows' source code.
Zombies in the compound indeed.
I hope Microsoft can deliver the revoked certificates in a trustworthy manner.
What could have however happened is that the said "Intelligence agency" first created a malware to infect MSFT engineers' computers and get access info of the code repository and then spoofing themselves as MSFT employees to download the source code. This is alot more plausible considering what stuxnet and flame can already do. (Assuming they were made by same "Intelligence agency")
MSFT should really check the systems of their employees first.
Microsoft licenses product source code to qualified customers, enterprises, governments, and partners for debugging and reference purposes
Drop 'em an email if you're curious.
Compaq couldn't just copy IBM's BIOS to make their new machine guaranteed IBM compatible, this would be illegal, and easily proven by IBM.
Solution: Reverse-engineer IBM's BIOS. Compaq used two sets of programmers - one group analyzed the original code and made notes of exactly how it responded.
The second group took these notes, and wrote their own BIOS that performed exactly the same.
Microsoft shared source initiative
http://www.microsoft.com/en-us/sharedsource/default.aspx
In 2003 MS gave China access to their source
http://www.microsoft.com/en-us/news/press/2003/feb03/02-28gs...