Add SSL-support for ICQ

[anonymous]

Would love to see SSL-support for ICQ via slogin.icq.com

[avery.barns@…]

Workaround: Using stunnel in client mode.

On the linux machine you have bitlbee installed , make stunnel listen on localhost:5190 and forward the connection to slogin.icq.com:443

Install stunnel (in ubuntu it's available in aptitude)

add -

[oscar]

client=yes

accept = 127.0.0.1:5190

connect = slogin.icq.com:443

- to /etc/stunnel/stunnel.conf

In bitlbee :

account icq set server 127.0.0.1

Worked fine for me. For now..

For various reasons my

PS , if you have troubles connecting at firt , modify this in stunnel.conf as well: sslVersion = all (I haven't tried this with the windows version of stunnel , but I'm sure it works just as well)

[avery.barns@…]

Somewhat related...

messenger.hotmail.com port 1863 is the standard port for msn messenger as far as I know..

Well .. messenger.hotmail.com port 443 does actually accept connections.. maybe it is a ssl door into msn , who knows ..

It would be nice to have the server variable available for MSN connections as well so there is room to test .

[avery.barns@…]

that 443 port on messenger.hotmail.com just seems to be https. Would be nice to have ssl support in msn in one way or another.

[wilmer]

Is it a simple matter of speaking MSNP over SSL on that port? It seems that it is not:

wilmer@peer:~/src/bitlbee/devel/protocols/msn$ openssl s_client -connect messenger.hotmail.com:443
CONNECTED(00000003)
[...]
VER 0 MSNP15 CVR0
HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Date: Mon, 18 Apr 2011 12:21:06 GMT
Connection: close
Content-Length: 311

It may be the odd MSNP-over-HTTP-proxy hack documented somewhere.

The OSCAR thing sounds good, I like the stunnel hack. BitlBee has SSL client code itself which could be used too.

[ilf@…]

Apparently it's simple SSL for ICQ. Adium can do this: ​http://trac.adium.im/ticket/9553 Since SSL code is already there, this shouldn't be hard, right?

[ilf@…]

<wilmer> icq-ssl? If someone gets it to work I'll accept the patch (assuming good code).
<wilmer> Not going to spend time on it myself.
<ilf> i'd assume it would be as easy as throwing existing ssl code on icq, no?
<wilmer> ilf: Yep, using ssl_connect() instead of connect and replacing all read/writes.
<wilmer> And fixing async I/O maybe.

Any takers? :)

[anonymous]

No Volunteers :(

Wilmer: You know the code best, you can probably do this in 15 minutes, no?

[wilmer]

I know BitlBee code, but the OSCAR module is one of those lovely pieces of code inherited from Gaim.

[anonymous]

libpurple/protocols/oscar/oscar.c has SSL code, can't we than just use that?

[dx]

Closing all OSCAR tickets, as ICQ switched to WIM which we don't support (the icyque purple plugin does)