Slashdot Mirror

← Back to Stories (view on slashdot.org)

MSN Messenger Kickbans Third-Party IM Clients

Posted by ryuzaki0 on from the turned-up-clocked-on-laid-off dept.

No_Weak_Heart writes "As reported here back in August, October 15th is the day Microsoft set to ban third party clients from logging in to their IM service. This eWeek article notes that the day is upon us, and MS is offering few details about its progress in creating licensing agreements to continue access. The licensing issue was previously discussed here. And my copy of Fire cannot log in. Anyone else find their IM clients non-responsive?"

18 of 422 comments (clear)

  1. Trillian seems ok by Stripes007 · · Score: 4, Informative

    My trillian .74F seems to be responsive

    --
    Stripes: Because stars are overrated
    1. Re:Trillian seems ok by mubar · · Score: 2, Informative

      I second that. Currently the upgraded Trillian Basic 0.74 F works just fine.

  2. aMSN by Anonymous Coward · · Score: 1, Informative

    new aMSN version works fine!
    amsn.sf.net

    Cheers.

    1. Re:aMSN by Anonymous Coward · · Score: 1, Informative

      I was using GAIM. Protocol failed. Downloaded latest CVS version. Still no dice.

      Downloaded aMSN for the first time. Works perfect.

    2. Re:aMSN by alok_naik · · Score: 2, Informative

      aMSN rocks ! Pretty much platform independent and no compiling required. I was using it on Solaris earlier and now on FreeBSD.

      --
      Every time I think I've hit the bottom, someone lends me a shovel.
  3. Working for me by phaze3000 · · Score: 4, Informative

    CenterICQ is working fine on MSN for me at present...

    --
    Blaming GW Bush for the Iraq war is like blaming Ronald McDonald for the poor quality of food.
  4. Miranda works! by CoreyGH · · Score: 2, Informative

    I'm using the MSN plugin that was included with Miranda IM version 0.3.1 I think that's the latest version. I have "Use MSN protocal v.8" checked in the options.

    1. Re:Miranda works! by RabidMonkey · · Score: 2, Informative

      Miranda is the best 'alternate' im client I've used ... it's features are great, file transfers seem to work where ICQ *AND* MSNs wont (although I can't get ICQ to work through my companys firewall, but their go.icq.com client does, so I must be doing something wrong - anyone seen an ICQ firewall plugin like the msn one that does http tunnels?

      I've gotten quite a few people to switch over, esp friends who ran both clients for years. Yes, it also supports Yahoo, but really, who uses yahoo?

      I think the best feature is all the coolass plugins that work so seamlessly.

      www.miranda-im.com

      --
      We emerge from our mother's womb an unformatted diskette; our culture formats us. - Douglas Coupland
  5. On a side note... by zakezuke · · Score: 3, Informative

    This is not directly attached to Messenger but rather their chat service.

    Oct 14th was the day they decided to also nix their free chat service in favor of their charge people roughly $20 a year for it.

    TK2CHATCHATA06 are 984 users and 45 invisible on 1 servers, this is roughly a 90% reduction from oct 13th.

    Why I bring this up you ask. Well very simple, msn is shooting them selves in the foot really. Their chat service it's very much possible they wanted roughly 90% of their population to leave, heck it's easier to manage. But the policy on Messenger clients, well I can't imagine anything really good will come out of banning 3rd party clients. Your typical user won't notice anyway, where as your power user with multi-clients will make a stand and leave for other services that work.

    But it looks good on paper, I imagine that's their pressent mission is with both Messenger and chat, making a good case for the shareholders why such services are money markers.

    --
    There is no sanctuary. There is no sanctuary. SHUT UP! There is no shut up. There is no shut up.
  6. Trillian 2.0... by SlashChick · · Score: 2, Informative

    ...works fine with MSN as of now.

    Anyone using an earlier version should upgrade to 2.0 to fix any MSN imcompatibilities.

    --
    Simpli - Your source for San Jose dedicated servers and colocation!
  7. Re:Gaim... by Stween · · Score: 5, Informative

    You're probably running an old version of Gaim if you're getting that message.

    MSN Protocol v9 has been supported for a version or two now.

    I just tried my Gaim 0.70 here (haven't updated to 0.71 yet), and it works perfectly. And it's quite definately not the 15th any more :)

  8. They have not "kickbanned 3rd-party clients" by grahamlee · · Score: 4, Informative

    What happened was that yesterday, the older MSNP8 protocol for accessing the MSN Messenger Network was discontinued; only clients capable of the new MSNP9 protocol can now connect.
    MSNP9 is actually better than the previous protocol (as well as incompatible :-( but you can't have everything) because it negotiates via the Secure Sockets Layer; i.e. your IMs are encrypted with a strong algorithm and cannot easily be read by people with NICs in promiscuous mode on your network hardware.

    There already exist third-party clients that can make use of this newer MSNP9 system; if your client does not then maybe it's worth (i)switching, (ii)asking the maintainers to add support, (iii)grabbing the source and doing it yourself you lazy wossname! However, Trillian frmo Cerulean Studios apparently does the business. I am currently connected to the MSN Network by Al's MSN; you must use at least v0.83 in order to connect.

    1. Re:They have not "kickbanned 3rd-party clients" by tunah · · Score: 2, Informative
      i.e. your IMs are encrypted with a strong algorithm and cannot easily be read by people with NICs in promiscuous mode on your network hardware.


      Actually, the IM part of the protocol has changed very little (at all?). What's changed is the login procedure. Previously, the server would send you a token, you would append your password and send them the MD5 hash. Now, the messenger server gives you some tokens, and you log onto passport, passing these on to the server. The passport logon uses HTTP with SSL, so your password is encrypted. The login process gives you the single-sign-in cookies (which unofficial clients ignore) and an authentication string to send back to the messenger server.


      It seemed to me that the login process was slower with MSN 6, I guess this is why - it requires about four HTTPS requests. (They optimised the contact list download protocol to reduce this slowdown).

      --
      Free Java games for your phone: Tontie, Sokoban
  9. Re:Jabber MSN Transports affected by Anonymous Coward · · Score: 1, Informative

    Make sure to install the latest transport on the jabberserver you're using :

    http://msn-transport.jabberstudio.org/

  10. What is the sound of one knee jerking? by TCaM · · Score: 2, Informative

    Ok maybe a few thousand knees.

    Seriously they announced this a while back as a PROTOCOL upgrade, they are locking out all older protocol versions, including I would assume ancient versions of their own messenger.

    Update your software people.

  11. Re:Gaim... by mrjb · · Score: 2, Informative

    tried installing 0.71 and got an error 'Protocol MSN failed to load." -- This can be fixed by installing SSL support first, THEN running ./configure, make and make install. SSL support reportedly can be installed with apt-get install gnutls7-dev, good luck all!

    --
    Visit http://ringbreak.dnd.utwente.nl/~mrjb/growingbettersoftware to download your free copy of the book
  12. Re:Just upgrade by Tony+Hoyle · · Score: 2, Informative

    What's worse is it doesn't use SSL beyond the first couple of packets... I wrote a proxy for MSN6 (needed to block file transfers through the firewall) and was amazed to find that after the initial SSL negotiation to establish identity, the entire protocol is still plaintext... certainly made writing the proxy easier :)

  13. MSNP9 DOES NOT ENCRYPT ! by Anonymous Coward · · Score: 1, Informative

    Some posters seem to be of the opinion that the new MSNP9 protocol encrypts their actual messages with SSL, this is wildly incorrect !! Only the .NET logon password transmission is encrypted, all messages are in plain text... Go Grab you favorite packet sniffer (http://www.ethereal.com/) and check for yourself, i did, it's all their in plain veiw of anyone... Then go get gaim-encryption (http://gaim-encryption.sourceforge.net/) get safe, be free ! Regards