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...
- Another Lawsuit Highlights How Many 'Smart' Toys Violate Privacy, Aren't Secure
- Israeli Government Pushes National Biometric Database With Claims Of Security Superiority Nobody Thinks Are True
- This Is A Really Bad Idea: Facebook, Twitter, YouTube & Microsoft Agree To Block 'Terrorist' Content
- FBI's NIT Hit 8,000 Computers In 120 Countries... As Did The Child Porn It Was Redistributing
- Russia Orders LinkedIn's Service To Be Blocked, Supposedly For Failing To Store Personal Data Locally