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...
- Judge Says The FBI Can Keep Its Hacking Tool Secret, But Not The Evidence Obtained With It
- Another Court Finds FBI's NIT Warrants To Be Invalid, But Credits Agents' 'Good Faith' To Deny Suppression
- FBI Agent Testifies That The Agency's Tor-Exploiting Malware Isn't Actually Malware
- Annoying Windows 10 Update Request Highlights Its Annoying-Ness On Live Weather Broadcast
- Just After EU Goes After Google For Antitrust, Microsoft Agrees To Drop All Antitrust Complaints About Google