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...
- DHS Offers Its Unsolicited 'Help' In Securing The Internet Of Things
- Lenovo Accused Of Locking Linux Out Of Certain Laptops At Microsoft's Request
- Hollywood Keeps Insisting Tech Is Easy, Yet Can't Secure Its Own Screeners
- Colin Powell's Email To Clinton About Personal Devices Shows Routing Around FOIA Is Business As Usual
- DRM: Still Hurting Paying Customers The Most