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...
- Nest Thermostat Goes From 'Internet Of Things' Darling To Cautionary Tale
- Ding-Dong -- Your Easily Hacked 'Smart' Doorbell Just Gave Up Your WiFi Credentials
- Copyright Blocking Security Research: Researchers Barred From Exploring Leaked Archive
- DailyDirt: Open Source Software In 2016
- If Microsoft Wins Its 'Stupid Patent Of The Month' Lawsuit, Expect A Plague Of Trolls To Move Into Design Patents