by Mike Masnick
Mon, Jun 4th 2012 7:37pm
We've discussed in the past just how dangerous our reliance on Certificate Authorities "signing" security certificates has become. This is a key part of the way we handle security online, and yet it's clearly subject to abuse. The latest such example: the now infamous Flame malware that targeted computer systems in the Middle East was signed by a "rogue" Microsoft certificate -- one which was supposed to be used for allowing employees to log into a remote system. Microsoft rushed out a security update over the weekend, but that doesn't change the core problem: the whole setup of relying so heavily on secure certificates seems to be increasingly dangerous.
If you liked this post, you may also be interested in...
- FBI Director Claims That The World's Most Knowledgeable Cybersecurity Experts Are Not 'Fair Minded' About Encryption Backdoors
- Pretty Much Anyone With Any Understanding Of Crypto Tells President Obama That Backdooring Crypto Is Monumentally Stupid
- Yes, Switching To HTTPS Is Important, And No It's Not A Bad Thing
- Ireland Becoming The Key Spot In Fights Over Data Privacy: Both Concerning Governments And Tech Companies
- Our New IP Czar Gives His First Speech... And It Is Not Encouraging At All