#711 closed enhancement (obsolete)

Add SSL-support for ICQ

Reported by: anonymous Owned by: Jelmer Vernooij
Priority: wishlist Milestone:
Component: OSCAR Version: 3.0
Keywords: SSL Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:


Would love to see SSL-support for ICQ via

Attachments (0)

Change History (10)

comment:1 Changed at 2011-04-14T09:56:27Z by 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

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

add -



accept =

connect =

- to /etc/stunnel/stunnel.conf

In bitlbee :

account icq set server

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)

comment:2 Changed at 2011-04-14T10:20:42Z by avery.barns@…

Somewhat related... port 1863 is the standard port for msn messenger as far as I know..

Well .. 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 .

comment:3 Changed at 2011-04-14T17:03:28Z by avery.barns@…

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

comment:4 Changed at 2011-04-18T12:23:09Z by 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
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.

comment:5 Changed at 2011-10-30T18:35:07Z by ilf@…

Apparently it's simple SSL for ICQ. Adium can do this: Since SSL code is already there, this shouldn't be hard, right?

comment:6 Changed at 2011-10-31T11:14:56Z by 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? :)

comment:7 Changed at 2012-05-21T17:53:53Z by anonymous

No Volunteers :(

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

comment:8 Changed at 2012-05-21T20:47:51Z by wilmer

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

comment:9 Changed at 2012-05-22T08:10:20Z by anonymous

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

comment:10 Changed at 2019-01-02T01:28:43Z by dx

Resolution: obsolete
Status: newclosed

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

Modify Ticket

as closed The owner will remain Jelmer Vernooij.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.