Install an XMPP (Jabber) server with Prosody [Updated]

Prosody packages are located in the Debian repository, but the developers of this software have prepared a repository for Debian and derivatives containing recent packages and additional modules, which we can use as follows:

echo "deb http://packages.prosody.im/debian stable main" | sudo tee -a /etc/apt/sources.list wget http://prosody.im/files/prosody-debian-packages.key -O- | sudo apt-key add - sudo aptitude update

Once the repository is added, we can proceed to install prosody (additionally adding modules to use sasl as an authentication mechanism if necessary, which allows to integrate prosody with pam, LDAP, Etc.).

sudo aptitude install sasl2-bin libsasl2-modules-ldap prosody liblua5.1- {sec0, cyrussasl0, event-prosody0}

We then proceed to generate self-signed certificates for our domain:

cd / etc / prosody / certs sudo openssl req -new -x509 -days 1095 -nodes -out "mydomain.cu.cert" -keyout "mydomain.cu.key"

The wizard will ask us a series of data, of which the really essential one is “Common Name (eg server FQDN or YOUR name) ”where we have to put our domain, as we will use it in the section virtual host configuration file.

Additionally, if on the server where we install prosody we have configured iptables With default deny policies, we need to open the required ports for our network, for example:

sudo iptables -A INPUT -i lo -j ACCEPT sudo iptables -A INPUT -i eth1 -s 192.168.0.0/24 -p tcp -m tcp -m state --state ESTABLISHED, RELATED -j ACCEPT sudo iptables -A INPUT - i eth1 -s 192.168.0.0/24 -p tcp -m tcp -m multiport --dports 5222,5223,5269 -m state --state NEW -j ACCEPT

Next, we proceed to modify some lines of the configuration file, for which we must edit /etc/prosody/prosody.cfg.lua so it looks like this:

ports = {5222, 5269} ssl_ports = {5223} admins = {"juan@mydomain.cu", "pedro@mydomain.cu"} use_libevent = true; - the default option is based on the select () function, instead libevent uses epoll (), which is more efficient and scalable. modules_enabled = {"roster"; "saslauth"; "tls"; "dialback"; "disk"; "private"; "vcard"; "privacy"; "compression"; "legacyauth"; "version"; "uptime"; "time"; "ping"; "pep"; "register"; - do not disable this module, it allows not only to register but also to change "adhoc" passwords; "admin_adhoc"; "posix"; "bosh"; - add this line if you want to enable jabber over http}; allow_registration = false; - disabled for security - change to true if you want to enable account creation from the client itself ssl = {key = "/etc/prosody/certs/localhost.key"; certificate = "/etc/prosody/certs/localhost.cert"; } storage = "internal"; - the default storage is an xml file - optionally we can use the "sql" storage method - this allows using SQLite, MySQL or PostgreSQL as a backend (although certain parameters must be added) authentication = "internal_hashed"; - we can use "internal_plain" if the client does not support SCRAM-SHA-1 - if we want to use the sasl method to later use LDAP, we must use "cyrus" log = {error = "/ var / log / prosody / prosody. err "; info = "/var/log/prosody/prosody.log"; } pidfile = "/var/run/prosody/prosody.pid"; VirtualHost "localhost" VirtualHost "mydomain.cu" ssl = {key = "/etc/prosody/certs/mydomain.cu.key"; certificate = "/etc/prosody/certs/mydomain.cu.crt"; }

Once the configuration file has been modified, we restart the service:

sudo service prosody subtract

sudo prosodyctl adduser juan@mydomain.cu sudo prosodyctl adduser pedro@mydomain.cu

sudo prosodyctl status

Prosody is running with PID 1310

Client configuration

Notes