Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>

Clone

HTTPS: git clone https://vervis.peers.community/repos/yEzqv

SSH: git clone USERNAME@vervis.peers.community:yEzqv

Branches

• master

Tags

jabber.mdwn

[[TODO|TODO/OPEN]] document everything I did, how to add and delete users, etc. and make SSL work! Monkeysphere seems to be more complicated but there’s no hurry with it

• prosody installation and config
• SSL for prosody
• SRV record in DNS
• citadel installation and XMPP config
• SSL for citadel XMPP

Certificate

Since the certificate needs to have all vhost and component domains, I used prosodyctl command to create a request and then import and sign using TinyCA. See here: http://prosody.im/doc/certificates.

But it seems that the domains don’t go into the crt file - either the norm, or a TinyCA issue. I didn’t try the cert yet, because for SRV I’ll need to set up my own nameserver here locally.

The talk.partager.null certificate still exists, in case it will be useful.

Users

I removed all previous users and created a single new user, which is also the only admin. I’ll use it to test everything.

SRV

This explains everything, do this after installing my nameserver: https://prosody.im/doc/dns.

Other links

• http://arstechnica.com/information-technology/2014/03/how-to-set-up-your-own-private-instant-messaging-server/

Controlling the server using the Jabber client

I need to set it up, see http://prosody.im/doc/modules/mod_admin_adhoc.

Components and MUC

I did just the basic step of adding a MUC component, but it’s a good idea to read about components, see what they offer, understand how to create and manage rooms: http://prosody.im/doc/components.

Security

Very good info here: http://prosody.im/doc/security.

But it seems that both stable and backports LuaSec versions are below 0.5 so I can’t have DH or ECDH without further tricks (luasec-prosody or testing/unstable).