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...
- T-Mobile Customer Data Leaked By Experian... And Faulty Encryption Implementation
- Microsoft 'Addresses' Windows 10 Privacy Concerns By Simply Not Mentioning Most Of Them
- DRM Still Breaking Games Nearly A Decade After Purchase
- CIA, FBI And Much Of US Military Aren't Doing The Most Basic Things To Encrypt Email
- Why Backdoors Always Suck: The TSA Travel Locks Were Hacked And The TSA Doesn't Care