|
RE: Is this issue caused by plus?
Assuming this was a server-side setting; one could assume that a small part of the Messenger department spent some modest time researching the risks and possible spreading through new versions. By simply initiating a forced update, the security still wouldn't be guaranteed and could cause double the discomfort, not to mention added negative reputation. Perhaps even a server side fix was needed to make sure the reported problem could not manifest itself in different forms. If that happens, it could lead to countless minor "fixes" and new versions of the worm along with it. Seems logical that as soon as they got their malfunction fixed with certainty when the service is used in conjunction with a specific build, they would force everyone to update to that build and re-enable options that caused risks before.
On a side note, I'm not one to trash talk Microsoft where it's not due, but I would say that it's not uncommon for Microsoft's services to be quite delayed when it comes to "minor" bugs. On the other hand, when a fix does arrive, it's usually very effective and not quick to be circumvented by users with malicious intentions.
This post was edited on 02-03-2011 at 05:37 PM by Arcticwolfx.
| 
/ 
