Comments on: QotW #31: What cryptographic flaw was exploited by Flame, to get its code signed by Microsoft? http://security.blogoverflow.com/2012/07/qotw-31-what-cryptographic-flaw-was-exploited-by-flame-to-get-its-code-signed-by-microsoft/ The Security Stack Exchange Blog Fri, 17 May 2013 09:35:18 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: mlevi2538@gmail.com http://security.blogoverflow.com/2012/07/qotw-31-what-cryptographic-flaw-was-exploited-by-flame-to-get-its-code-signed-by-microsoft/#comment-10556 mlevi2538@gmail.com Tue, 23 Oct 2012 22:37:38 +0000 http://security.blogoverflow.com/?p=733#comment-10556 very useufl inforamtion. thanks

mlevi2538@gmail.com

]]> By: What is SHA3 – and why did we change it? « Stack Exchange Security Blog http://security.blogoverflow.com/2012/07/qotw-31-what-cryptographic-flaw-was-exploited-by-flame-to-get-its-code-signed-by-microsoft/#comment-9944 What is SHA3 – and why did we change it? « Stack Exchange Security Blog Fri, 12 Oct 2012 12:05:33 +0000 http://security.blogoverflow.com/?p=733#comment-9944 [...] Now, onto hashing. Way back in 1996, discussions were underway in the cryptographic community on the possibility of finding a collision within MD5. Practically MD5 started to be commonly exploited in 2005 to create fake certificate authorities. More recently, the FLAME malware used MD5 collisions to bypass Windows signature restrictions. Indeed, we covered this attack right here on the security blog. [...]

]]>