• Encrypted internal chat solution
• All traffic stay inside you organization
• Can federate and chat with other organizations in a secure manner
• Can add global rules for blocking links, file transfers and unpatched clients
• Can add MSN contacts and be sure that messages with links is blocked server-side

In addition to secure chat OCS gives the businesses the ability to implement Unified Communications and is therefore way more than just a chat client.

About this trojan

First you get a message from one of you contacts saying, seen this?? :D  and it links to hxxp://www.facebook-c.com/image.php?Photo023girl.JPG. The trojan adapts to the language on the computer and will display the text in you native language. In norwegian it will be se på dette bildet :D with the link following. The link points to a site at Yahoo and so the links was live for a day or two. It still was a huge security risk. The trojan is written in Visual Basic and executes a C++ program. It installed itself as c:\windows\winmbu.exe and granted itself access through the local firewall. The program gave the owner of the trojan access to

• Communication with C&C over the IRC protocol
• Sending of messages over MSN and Yahoo messenger
• Download and run files on the infected computer

At release date only 13 of 41 antivirus products detected this file. So even with an updated antivirus on the local computer 69% of the antivirus solutions would not have detected it.

Link to official article in norwegian: http://telenorsoc.blogspot.com/2010/03/trojaner-spres-via-msn-messenger.html
Link to the antivirus protection overview: http://www.virustotal.com/analisis/89c677bc0044864d80244aee8201661e79f431f33c3b164aa778f363fe1cf9da-1267474859

Read the entire post here: http://www.milkaddict.com/?p=21

How does Windows Live Messenger works? there are millions of users typing messages everyday but maybe few of them ever asked themselves how the messenger really works! so here I wrote a little post about it. Windows Live Messenger it’s an hybrid Client-Server / Peer-to-Peer application. It basically started as a client-server application. Let’s say that the client A wants to contact the client B. The client A logs in a CS (Connection Server) through a persistent TCP connection (eventually using proxy,gateway..). Behind the CS there are the PS (Presence Server). Each person get always the same particular PS, which is where your personal status message, description of your user photo and similar things are stored.

Another element of the architecture is the Address Book. The client A gets directly from the Address Book his list of contacts. Then the client A tells to his CS who his friends are, the CS subscribes to his friend’s PS to get the presence information that are sent up through the client server connection. If the client A change his status to OffLine for example, the change goes up to the CS of A, then to the PS of A, then down to the CS of B through the subscription and then down to the client B.

CHAT

If the client A wants to chat, tells to his CS that wants to contact somebody, and the CS tells A to contact a Mixer, which sends IM traffic to a destination, for example to B (passing through the CS of B). Then A and B and talk back and forth through the Mixer.

You can watch also an original video where some of the developers and visionaries behind Windows Live Messenger explain how it works. http://channel9.msdn.com/posts/Charles/Windows-Live-Messenger-What-How-Why/