|
|
|
|
Screenshot
Windows Live Messenger 8.5 conversation window |
|
| Developed by | Microsoft |
| Initial release | December 13, 2005 (2005-12-13) |
| Latest release | 2008 (Build 8.5.1302.1018) / November 6, 2007 |
| Preview release | 2009 (Build 9.0.1407.1107) / November 16, 2007 |
| OS | Microsoft Windows and Xbox 360 |
| Genre | Instant messaging client |
| License | Adware |
| Website | http://messenger.live.com |
Windows Live Messenger is an instant messaging client for Windows XP, Windows Server 2003, Windows Vista, and Windows Mobile, first released on December 13, 2005 by Microsoft.[1] It is the successor to MSN Messenger. It is part of Microsoft's Windows Live set of online services. The current stable version is Windows Live Messenger 2008 (also known as version 8.5), which was released on November 6, 2007.
The client connects to Microsoft's .NET Messenger Service. Corporations can also integrate their Live Communication Server and Active Directory with the network on behalf of its clients. Most major multi-protocol clients can also connect to the service.
Contents |
To the features available in MSN Messenger, Windows Live Messenger adds the following:
The Sharing Folder feature of Windows Live Messenger is an alternative to the "direct transfer" method of file distribution. When a user wants to deliver a file to another person on his or her contact list, the "sharing folder" window appears, which is an individualized representation of all previously shared items.
When files are added to the "sharing folder" for that particular person, the file will automatically be transferred to the corresponding computer when they are online. This means that the folder is literally "shared" between two computers. If a user deletes a file, for example, the file will also be deleted from the corresponding computer's shared folder.
To minimize risk of virus-infected transfers, the "sharing folder" feature is bundled with an anti-virus program. The "sharing folder" feature can only be used on computers with NTFS-formatted hard disks.
In addition to PC-to-PC calls that have been supported in previous versions, Windows Live Messenger now supports PC-to-phone calls with Windows Live Call. In the US, this feature is supported by Verizon, branded as "Verizon Web Calling". Orange France also has a similar service. This feature is only available in selected countries, including the US, the UK (Verizon planning to end service in August 2008), France, Germany, the Netherlands, Austria, Ireland, Finland, Belgium, Spain, and Italy.
On October 13, 2005, Yahoo! and Microsoft announced plans to introduce interoperability between their two messengers,[2] creating the second largest instant messaging user base worldwide: 40 percent of all users. The announcement comes after years of third-party interoperability success (most notably, Trillian, Pidgin) and criticisms from Google that the major real time communications services were locking their networks. Microsoft has also had talks with AOL in an attempt to introduce further interoperability, but so far, AOL seems unwilling to participate.[citation needed]
Interoperability between Yahoo! and Windows Live Messenger was launched 12 July, 2006.[3][4] This allows Yahoo! and Windows Live Messenger users to chat (using text or voice) to each other without the need to create an account on the other service, provided both contacts use the latest versions of the clients. However, if a user uses an older or third-party client, they will appear offline to the users on the other network.
Windows Live Messenger 9 is expected to improve multi-client support, adding Google Talk, AOL, ICQ and Jabber to the list.[citation needed]
Unlike previous versions, one can send messages to contacts who are offline; they will receive the messages once they come online.
Additionally, one can start conversations even when his or her status is set to Appear Offline, similar to behaviour in Yahoo! Messenger and ICQ. If talking to someone who has an older MSN Messenger client, they will lose the ability to talk to you after a short period of no activity, due to their client thinking you are offline. As Windows Live Messenger has now been made available on several phones, a new trend has appeared where people send messages over Windows Live Messenger to each other through an Internet connection, rather than SMS messages.
There are various games and applications available in Windows Live Messenger that can be accessed via the conversation window by clicking the games icon and challenging your "buddy".
The i’m initiative is a program Microsoft launched in March 2007, that connects the user with nine organizations dedicated to social causes through Windows Live Messenger, only for conversations sent or received in the USA. Every time someone has a conversation using i’m, Microsoft Corp. shares a portion of the program's advertising revenue with the organization of the user's choice. There is no set cap on the amount donated to each organization. The more i’m conversations the user has, the more money goes to one of the nine causes. Each participating organization is guaranteed a minimum donation of $100,000 during the first year of the program. There is currently no end date for the program.[5] The i’m initiative works with version 8.1 and above.
Windows Live Messenger support was included in the Xbox 360 Spring 2007 dashboard update released on May 9, 2007.[6] Unofficially, it is known as Windows Live Messenger 360.
Those using Windows Live Messenger are able to see the Gamertags of friends logged into Xbox Live, including the game they are playing. Xbox 360 users can chat in-game (or while watching a movie). Although only text chat is supported, Microsoft has suggested that voice and video chatting may come in a future update.
Also to coincide with the arrival of the integration of Windows Live Messenger with Xbox Live, Microsoft released a new Xbox 360 keyboard adaptor called Xbox 360 Chatpad for easier text input. The keyboard device attaches to the standard Xbox 360 controller through the headphone jack and features a QWERTY-style key layout with 47 keys, although any USB keyboard will work just as well with an Xbox 360.
As of December 4, 2007, a child account can now use Windows Live Messenger on Xbox Live.
A client for Windows Live Messenger was developed by Microsoft for the Symbian S60 Platform commonly used in mobile phones such as Nokia smartphones and released on 23 August 2007 to selected markets. This version of Windows Live Messenger includes many of the features of the Windows Live Messenger client, including grouped contacts, voice clips, image and file sending; as well as features unique to S60 such as tabbed chat windows and integration with contact list and other features of the S60 platform. [7] Microsoft installed a prompt at the start of Windows Live Messenger for S60 at Logon [8] When the trial expires the cost to users of Messenger for S60 is £1.50/$2.94 for 30 calendar days of use.
Windows Live Messenger uses the Microsoft Notification Protocol (MSNP) over TCP (and optionally over HTTP to deal with proxies) to connect to the .NET Messenger Service—a service offered on port 1863 of messenger.hotmail.com. Its current version is 15 (MSNP15), used by Windows Live Messenger and other third-party clients. MSNP15 introduces a different authentication mechanism. The protocol is not completely secret; Microsoft disclosed version 2 (MSNP2) to developers in 1999 in an Internet Draft, but never released versions 8, 9, 10, 11, 12, 13, or 14 to the public. .NET Messenger Service servers currently only accept protocol versions from 8 and on, so the syntax of new commands from versions 8 through 14 is only known by using packet sniffers like Wireshark.
Windows Live Messenger (along with other networks such as Yahoo! Messenger and AOL Instant Messenger) is often used as a conduit or "vector" for delivering malicious software such as spyware, viruses, worms, and trojans to unsuspecting computer users. The two methods used by hackers to deliver malware over the IM vector are (1) sending a file transfer with a virus-infected file, and (2) delivering a message with socially engineered content containing a web address (URL) containing active malicious code. Viruses and worms with colorful names such as W32.Yalove or Troj/Msnfake-L have been identified as targeting users of the Windows Live Messenger network (and the former MSN Messenger network) over the past few years.
The threat of infection by these two methods is substantial and growing. The IM Security Center, a collaboration between security companies and corporations, has tracked attacks over IM since 2003 and shows well over 1000 distinct attacks over the public IM networks. The first half of 2007 saw an 84% increase in IM attacks over the first half of 2006. While IM-specific attacks remain a small percentage of overall virus and malware threats, the continued growth in usage of IM, along with the rapid adoption of IM in the workplace (See Instant Messaging) make IM an attractive vector for hackers, and both individuals and companies must take precautions to avoid infection.
The most common method of delivering a malicious payload is the use of social engineering to construct a message that appears to be coming from a contact on the recipient's contact list. A socially engineered message is one that is written in a friendly, informal manner, that could easily be mistaken as coming from a friend. The message usually will say something like "Click here to see pics of me from vacation!" or "Is this you?" with a web address -- known as a "poison URL" -- for the recipient to click. Upon clicking the web address, the recipient is connected to a website containing active content, which is immediately downloaded to the recipient's computer. In most cases, the payload contains an installer, a number of hidden files containing text, and code which causes the same socially engineered message with poison URL to be sent to every contact on the contact list. When the message is sent to all contacts, the cycle starts again, as each contact believes they are receiving a message from a trusted friend. In this manner, IM-borne malware is capable of propagating very rapidly through company and external networks.
Worms and viruses are discovered on a regular basis by security companies, particularly by the three companies with network-certified IM-specific security products, Akonix Systems, FaceTime Communications, and Symantec. According to IM security researchers at Akonix, the mean number of new threats per month identified during the period January 2006 through August 2007 is 34, with a high of 88 in October 2006, and a standard deviation of 19.[9]
People can set up Windows Live Messenger to use their own PC anti-virus software to scan all the files they receive through IM and File Sharing by using the File Transfer Options.[10] There are no further instructions how to make this work, but the option to use Windows Live OneCare Safety Scanner is possible and working.
On September 12, 2007, the Windows Live Messenger blog posted an entry that reported of a security vulnerability discovered in versions of Messenger older than 8.1. The vulnerability "could allow remote code execution when a user accepts a webcam or video chat invitation from an attacker. An attacker who successfully exploited this vulnerability could take complete control of the affected system." This led to an auto-update being released to all older versions. Versions running on Windows 2000 and below were required to update to a new version of MSN Messenger 7.0, and versions running on Windows XP and above were required to update to Windows Live Messenger 8.1.[11]
Some add-ins are available to modify Live Messenger, enable hidden features, or extend capabilities. They include:
The first beta was released on December 13, 2005.[1] It remained online and usable for around a month until an auto-update feature forced one to install Beta 2, rendering this version obsolete. Major changes and additions include:
Known bugs within this version include the offline conversation feature: although still advertised in the yellow bar at the top of the conversation box, it is useless to anyone who had not received an invitation (i.e., downloaded it from another site).[12]
The second beta was released on February 26, 2006.[1] The overall theme of this version was improved, fixing and improving several smaller places in the program. This version has become obsolete, forcing users to update the program. Major changes and additions include:
This beta was released on May 2, 2006,[1] was nearly identical to the final. Major changes and additions include:
The final and official release of Windows Live Messenger was made on June 19, 2006.[1] No notable changes were made between Beta 3 and this version.[15]
This version, released on August 10, 2006,[1] included audio and video improvements, and fixed up minor bugs.[16]
This beta version of Windows Live Messenger, released on October 30, 2006.[1] No major changes were made, but several minor changes were included. These changes made include:
The Refresh of Windows Live Messenger Beta 1, released on December 13, 2006,[1][18] fixed bugs which were causing some people to be unable to sign in and others unable to see their contact list.
Released on January 29, 2007.[1] No actual changes were made from Beta 1 refresh.[19] As of September 12, 2007, all versions of Windows Live Messenger below version 8.1 are now rendered obsolete due to a security issue identified when a user accepts a webcam or video chat invitation from an attacker.[20]
On May 27, 2007, LiveSide reported a leaked build of Windows Live Messenger 8.5, available in Spanish.[21] The English beta build was later released on May 31, 2007[1] to the US, UK, Canada, Ireland, India, France, Japan, Germany, China and Spain. An update was released on June 21, 2007, to test updates being installed by Microsoft Update.
Major changes and additions include:
The second beta was released on September 5, 2007[25] Several issues were fixed on Beta 2 but no significant changes were applied. Compared with the first beta, the build does not say "Beta" on the top of the window, although developers had noted that it was not the final release. It is notable that the new Windows Live Installer, which is used to install Windows Live Messenger 8.5, does not run on Windows Server 2003.
The final version of Windows Live Messenger 8.5 was released on November 6, 2007.[26]
|
|
This article or section contains information about computer software currently in development. The content may change as the software development progresses. |
|
Windows Live Messenger 9 is currently in development. In a Presentation to the Georgia Institute of Technology's IEEE Student Branch, Microsoft employee and Georgia Tech Andrew Jenks announced that it will ship "in late 08 or early 09".
Internal builds are already at WLM 9 and includes many of the API components. They have a team working on multi-person audio/video chat for WLM that may or may not be in version 9, but is expected to be in by 10. They are also attempting to work out a way for WLM users to chat with AIM/XMPP/ICQ users like the way Yahoo! Messenger works now, and they have a basic internal version that works with Jabber already.[27]
Features published by the news site Liveside include specialized features against messaging spam, the ability to stay signed into the application from several computers (referred to as "Multiple Points of Presence Support"), animated GIF files in the photo area, per-contact customized sounds for various user actions, and clickable URLs in the status area.[28]
On November 20, 2007, an invitation to participate in the Windows Live Messenger 9 Beta was sent out to beta testers on http://connect.microsoft.com/. Later on November 27, 2007, Microsoft began sending out emails to beta testers, welcoming them to the Windows Live Messenger 9 Beta program.
The current beta version of WLM 9, in contrast with current stable versions of Windows Live Messenger, does not include the device manager. This resulted in some WLM-compatible devices not functioning, including the official Live Messenger Phone.[citation needed]
|
||||||||||||||
|
||||||||||||||||||||||||||
Why are we here?
All text is available under the terms of the GNU Free Documentation License
This page is cache of Wikipedia. History