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...
- Homeland Security Starts Banning Laptops & Tablets On Planes From The Middle East
- Smart Vibrator Company To Pay $3.75 Million For Private Data Collection
- Consumer Reports Proposes Open Source Security Standard To Keep The Internet Of Things From Sucking
- Sony, Microsoft Lobby Against Right To Repair Bills (Yet Refuse To Talk About It)
- Court Says Microsoft Can Sue Government Over First Amendment-Violating Gag Orders