Home › Forums › Archives › Site News & Announcements › Instant Messaging News › Windows Live Messenger News › Microsoft to kill Windows Messenger
- This topic has 0 replies, 1 voice, and was last updated 20 years, 6 months ago by BigBlueBall News.
-
AuthorPosts
-
October 29, 2003 at 6:00 am #16264BigBlueBall NewsMember
detn8r
October 29, 2003
Windows Messenger service, a function used to exchange data between computers unrelated to MSN Messenger, has become more trouble than its worth in recent months since spammers latched onto the service as a way of launching pop-up spam boxes on targeted PCs. The service was also subject to a security flaw this month which created a mechanism for crackers to commandeer vulnerable Windows boxes. Microsoft has issued a patch but even so, the problem is another black mark against a not-terribly-useful service.
So Microsoft has decided to turn off Messenger services with Windows XP Service Pack 2, due in the first half of next year. Microsoft is yet to detail how it intends to disable the service on other versions of Windows. Windows Messenger service is seldom used by consumers; and businesses, which might use it, have the expertise to turn the service back on.
Last week, AOL took the unilateral decision to kill off Windows Messenger service for its subscribers.
Security Fence
Microsoft execs this week outlined various plans to improve Windows security at the firms Professional Developer Conference in Los Angeles.
IDG(http://www.infoworld.com/article/03/10/28/HNmessengeroff_1.html) reports that Microsoft is developing a new API (application programming interface) for RPCs (remote procedure calls) to more tightly control the operation of the protocol in MS environments. The security shortcomings of Microsofts implementation of RPC within its distributed component object model (DCOM) were highlighted by the devastating Blaster worm. Further Microsoft security alerts about this same RPC component of Windows since the August spread of Blaster have merely underlined the problem.
Microsoft also plans to apply more restrictive default configurations on its ubiquitous Internet Explorer web browser Local Machine and Local Intranet security zones.
Source: The Register
-
AuthorPosts
- You must be logged in to reply to this topic.