Slashdot Mirror
In Face of Flame Malware, Microsoft Will Revamp Windows Encryption Keys
coondoggie writes "Starting next month, updated Windows operating systems will reject encryption keys smaller than 1024 bits, which could cause problems for customer applications accessing Web sites and email platforms that use the keys. The cryptographic policy change is part of Microsoft's response to security weaknesses that came to light after Windows Update became an unwitting party to Flame Malware attacks, and affects Windows XP, Windows Server 2003, Windows Server 2003 R2, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems."
Citation: my contacts at Microsoft and apple. Obviously I can't name names.
Well, until MS explains what the NSAKey does, I'll just assume the worst.
You say that lots of governments can look at the Windows source code, but I have some news to you.
1 - They can't look at the entire code, some sections don't live Microsoft's headquarters, and that is known because...
2 - The code doesn't compile. You aren't allowed to compile it anyway, and it is clearly documented that it doesn't. Also, the tools needed for compiling it aren't simply available.
Informations took from the best of my efforts squeezing people that had contact with the situation and MS salespeople. (And if you are wondering, yes one can squeeze information from MS salespeople, you just need to be better than a lawyer when making your questions less prone to distortion and requiring an answer that actualy answers it. If you are in a position of power, after a few tries you'll get some information - not complete answers, just some information - and the salesperson will run away.)
Rethinking email