JJB Blog

NOTE: updated instructions can be found here.

The current beta of Adium [http://adiumx.com] does not support SSL for Jabber. But you can “force” it to do so by enableing SSL at the OS level. Here’s how:

[1]: if Adium is running, quit it.

[2]: get ssl enabler: http://www.apple.com/downloads/macosx/unix_open_source/sslenabler.html and map jabber.org to 5223 on both ends. ssl enabler forces all traffic through a specific port to a specific place to use ssl, and the application (in this case, Adium) doesn’t have to know about it. note: for debugging purposes, you can do the same with port 5222. then if something is wrong and adium is still sending over 5222, the jabber server will tell you that you can’t do ssl on that port. that way you will know if the below changes worked (and that adium is indeed using the correct port).

[3]: change the port that adium uses for jabber from 5222 to 5223. this can be done using Property List Editor on the following two files (just double click on them in the finder or use open <filename> at the command line), which i found with grep as shown:

john@g5bachir:/Applications/Adium.app/Contents$ grep -rI 5222 * 2> /dev/null
PlugIns/Gaim.AdiumPlugin/Contents/Resources/GaimServiceDefaults.plist:  5222
Resources/GaimServiceDefaults.plist:    5222

i’m not sure if changing the default is necessary but i did it just in case.

[4]: now i will admit my complete ignorance regarding how NAT works and my partial ignorance about tcp/ip in general. I also opened up port 5223 on my firewall and forwarded port 5223 on my router to my machine. i’m pretty sure that neither of these was necessary, considering that port 5222 was not opened or forwarded before i enabled ssl, and jabber was working.

now fire up Adium. ta da!

ShareThis