Switch MSN implementation to XMPP

[anonymous]

Microsoft has announced their ​plans to make the Windows Live Messenger services ​available over XMPP.

It'd be extremely nice to see bitlbee support this.

[anonymous]

It looks like it uses a different authentication mechanism, also, it apparently lacks roster management.. so not really a suitable replacement for the reverse engineered MSN protocol backend.

[wilmer]

Indeed it's stripped down, like Facebook's XMPP. I'll try to get the XMPP module to support the authentication scheme though, since for day-to-day things it's likely much nicer, and it'll always be a nice fallback when the native MSN module stops working.

[wilmer]

Success!

18:34:21 <@root> jabber - Logging in: Server changed session resource string to 
                 `{e5f84c99-51bc-4a3b-ace2-53d60a99daa5}'
18:34:21 <@root> jabber - Logging in: Authenticated, requesting buddy list
18:34:21 <@root> jabber - Logging in: Logged in
18:34:22 -!- _65fa8ab93184d611 [65fa8ab93184d611@messenger.live.com] has joined &bitlbee
18:34:22 -!- ServerMode/&bitlbee [+v _65fa8ab93184d611] by peer.bitlbee.org
18:34:22 -!- _2cf8192c9204b909 [2cf8192c9204b909@messenger.live.com] has joined &bitlbee
18:34:22 -!- ServerMode/&bitlbee [+v _2cf8192c9204b909] by peer.bitlbee.org

But the handles definitely suck. At least WHOIS helps:

18:34:27 -!- _65fa8ab93184d611 [65fa8ab93184d611@messenger.live.com]
18:34:27 -!-  ircname  : Wilmer
18:34:27 -!-  server   : blurp@messenger.live.com. [jabber network]
18:34:27 -!- End of WHOIS
18:34:31 -!- _2cf8192c9204b909 [2cf8192c9204b909@messenger.live.com]
18:34:31 -!-  ircname  : Sjoerd
18:34:31 -!-  server   : blurp@messenger.live.com. [jabber network]
18:34:31 -!- End of WHOIS

This is definitely not useful enough to drop native MSN support. Worst part is, it seems that there is no way to get a token that lasts for more than an hour, so you'll have to do the "authorize in browser, pass authentication code back to BitlBee" dance again every time you log in..

[wilmer]

changeset:xmpp-oauth,815 should have this now. If you want to try it out:

19:39:21 <@wilmer> ac add jabber foo@messenger.live.com bla
19:39:21 <@root> Account successfully added with tag jabber
19:39:28 <@wilmer> ac jabber set oauth on
19:39:28 <@root> oauth = `on'

Something like that should work. Please let me know how that goes.

I think the nightly build bot will automatically pick up this branch within the next few hours.

[wilmer]

Oh yes, you probably want to add a "ac jabber set nick_format %full_name" there too.

[wilmer]

Well, this stuff works. But it's not going to be ready for replacing the "native" MSN module any time soon.

Fixed for as much is reasonable.

[deferraz@…]

I tried on 3.0.5 release and set oauth to on but i'm receiving this:

.:18:11:39:. @root: jabber - Logging in: Connecting .:18:11:39:. @root: jabber - Logging in: Connected to server, logging in .:18:11:39:. @root: jabber - Logging in: Converting stream to TLS .:18:11:39:. @root: jabber - Logging in: Connected to server, logging in .:18:11:40:. @root: jabber - Login error: BitlBee does not support any of the offered SASL authentication schemes:

X-MESSENGER-OAUTH2

There is some other thing to set?

[wilmer]

That's fixed now.