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...
- Telegraph Publishes The Dumbest Article On Encryption You'll Ever Read... Written By David Cameron's Former Speechwriter
- Gmail Takes A Sledgehammer To The Techdirt Daily Newsletter When Not Even A Scalpel Is Needed
- Chipotle Exposes Private Data By Sending HR E-mails Via Unowned Domain, Doesn't See The Problem
- Guy Sues Google And Bing For Returning Photos Of Him In Search Results
- Microsoft 'Addresses' Windows 10 Privacy Concerns By Simply Not Mentioning Most Of Them