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...
- Emails Show Hillary Clinton's Email Server Was A Massive Security Headache, Set Up To Route Around FOIA Requests
- The Campaign To Dox Twitter Users In Islamic Countries For 'Blasphemy' And Supporting LGBT Rights
- DailyDirt: Big Data Isn't Necessarily Better
- FBI Sends Computer Information Collected By Its Hacking Tools In Unencrypted Form Over The Open Internet
- Top Internet Companies Agree To Vague Notice & Takedown Rules For 'Hate Speech' In The EU