Comment by K0nserv

I was under the impression the underlying issue has been patched. If it hasn't, this page and their initial blog post seem irresponsible. If it has indeed been patched why not provide a detailed write up?