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...
- Akamai: 12-Year-Old SSH Vulnerability Fueling Internet-Of-Broken-Things DDoS Attacks, And Worse
- Government Seeks Do-Over On Win For Microsoft And Its Overseas Data
- Two More Courts Find In Favor Of The FBI And Its NIT Warrant; No Suppression Granted
- Verizon Wants $1 Billion Discount After Yahoo Scandals, Still Fancies Itself The New Google
- Basically All Big Tech Companies Deny Scanning Communications For NSA Like Yahoo Is Doing