jabberd 2.0: ssl problems, aim-transport

[infiniteedge]

I just installed and configured jabberd 2.0 by unmasking the package in portage. I tried configuring it for SSL connections. I used the self-cert.sh script to generate an openssl cert and then pointed the router to it, and set in the router configuration in all the other config files to use that cert. It is also included in the c2s.xml file for client communications. Setting require starttls causes logins to fail on the authentication step. People can login and talk on the server fine when require starttls is not set.

UPDATE: Ah Ha! self-cert.sh creates the key in the wrong directory. It makes it in /etc/jabber/gentoo.pem (jabber 1.4's config directory) instead of /etc/jabberd/gentoo.pem (jabber 2.0's config directory). I will file a bug for this.

Also:
The jabber docs talk about Jabber Component Runtime (JCR), MU-Conference, Jabber Users Directory (JUD), and perl Users-Agent... but it doesn't really give me a clear picture of what they do, when I would need them, or if they work on server version 2.0. Can someone help me out? I'm lost, I've never used jabber before 2 days ago. What I want is a full-featured jabberd 2.0 server with AIM, MSN, and possibly Yahoo-transports (most importantly AIM).

One more thing:
Passwords to users are stored in plaintext in MySQL. Is there a way to force them to be encrypted in storage?

Thanks.

relevant links:
http://jabberd.jabberstudio.org/2/docs/
http://aim-transport.jabberstudio.org/
http://pyaim-t.blathersource.org/
http://jud.jabberstudio.org/
http://jabber.terrapin.com/JCR/