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...
- Microsoft Sort Of Addresses Windows 10 Privacy Complaints With New Privacy Dashboard
- FTC Sues D-Link For Pretending To Give A Damn About Hardware Security
- After Lawsuits And Denial, Pacemaker Vendor Finally Admits Its Product Is Hackable
- Ex-MI6 Boss: When It Comes To Voting, Pencil And Paper Are 'Much More Secure' Than Electronic Systems
- Microsoft Finally Admits Its Malware-Style Windows 10 Upgrade Sales Pitch Went Too Far