It was only a matter of time before someone decided to exploit that issue. I read about the issue a few weeks back and applied a temp fix to the 2.0.10 build we were running. I was not yet ready to upgrade to 2.0.11, so I figured it would suffice.
We're all patched up at this point to 2.0.11. Hopefully 2.0.11 truly isn't affected as suggested by the article.
I heard it was a pain, but f-secure was one of the people trying to contact google to fix the issue. I guess it took about 7 hours for them to fix the issue. Seven hours is reasonable to me. At least they addressed the issue.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.