~9AM on 8/12: Bug was reported to VMware and several other sites.
~Noon on 8/12: VMware had the workaround (set date back on ESX hosts)
~10PM on 8/12: Fix was released
This article was posted on 8/13. Get your facts straight before saying that a patch hasn't been released. While I'm dissapointed VMware let this slip through their QA, I'm very impressed with how quickly they responded to the issue.
Discussion on:
Message 4 of 1
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox



