From 923dfb49df8e3a094d19ca984fdc822cb8d1e294 Mon Sep 17 00:00:00 2001 From: Alexander Dahl Date: Fri, 18 Nov 2022 09:30:12 +0100 Subject: [PATCH] :bento: prosody: Import existing configuration files No changes reported by ansible to what's currently deployed. --- host-pottwal.yml | 30 +++ templates/prosody/jabber.n39.eu.cfg.lua.j2 | 36 ++++ templates/prosody/localhost.cfg.lua.j2 | 5 + templates/prosody/prosody.cfg.lua.j2 | 227 +++++++++++++++++++++ 4 files changed, 298 insertions(+) create mode 100644 templates/prosody/jabber.n39.eu.cfg.lua.j2 create mode 100644 templates/prosody/localhost.cfg.lua.j2 create mode 100644 templates/prosody/prosody.cfg.lua.j2 diff --git a/host-pottwal.yml b/host-pottwal.yml index 4d910f0..0668636 100644 --- a/host-pottwal.yml +++ b/host-pottwal.yml @@ -125,6 +125,36 @@ msg: "prosody data dir is missing, please restore from the backup!" when: not prosody_dir.stat.exists + - name: Ensure prosody main config file is in place + ansible.builtin.template: + src: "templates/prosody/prosody.cfg.lua.j2" + dest: "{{ prosody_data_dir }}/etc/prosody/prosody.cfg.lua" + mode: 0644 + + - name: Ensure prosody localhost config file is in place + ansible.builtin.template: + src: "templates/prosody/localhost.cfg.lua.j2" + dest: "{{ prosody_data_dir }}/etc/prosody/conf.avail/localhost.cfg.lua" + mode: 0644 + + - name: Ensure prosody localhost config symlink exists + ansible.builtin.file: + src: "../conf.avail/localhost.cfg.lua" + dest: "{{ prosody_data_dir }}/etc/prosody/conf.d/localhost.cfg.lua" + state: link + + - name: "Ensure prosody {{ prosody_domain_name }} config file is in place" + ansible.builtin.template: + src: "templates/prosody/{{ prosody_domain_name }}.cfg.lua.j2" + dest: "{{ prosody_data_dir }}/etc/prosody/conf.avail/{{ prosody_domain_name }}.cfg.lua" + mode: 0644 + + - name: "Ensure prosody {{ prosody_domain_name }} config symlink exists" + ansible.builtin.file: + src: "../conf.avail/{{ prosody_domain_name }}.cfg.lua" + dest: "{{ prosody_data_dir }}/etc/prosody/conf.d/{{ prosody_domain_name }}.cfg.lua" + state: link + - name: Ensure container for prosody XMPP server is running docker_container: name: prosody diff --git a/templates/prosody/jabber.n39.eu.cfg.lua.j2 b/templates/prosody/jabber.n39.eu.cfg.lua.j2 new file mode 100644 index 0000000..47d99ef --- /dev/null +++ b/templates/prosody/jabber.n39.eu.cfg.lua.j2 @@ -0,0 +1,36 @@ +-- Section for example.com + +VirtualHost "jabber.n39.eu" + + -- Assign this host a certificate for TLS, otherwise it would use the one + -- set in the global section (if any). + -- Note that old-style SSL on port 5223 only supports one certificate, and will always + -- use the global one. + ssl = { + key = "/etc/prosody/certs/jabber.n39.eu.key"; + certificate = "/etc/prosody/certs/jabber.n39.eu.pem"; + dhparam = "/etc/prosody/certs/dh-2048.pem"; + -- TODO for post 0.10 see http://prosody.im/doc/advanced_ssl_config again + options = { "no_sslv2", "no_sslv3", "no_ticket", "no_compression", "cipher_server_preference", "single_dh_use", "single_ecdh_use" }; + } + +------ Components ------ +-- You can specify components to add hosts that provide special services, +-- like multi-user conferences, and transports. +-- For more information on components, see http://prosody.im/doc/components + +-- Set up a MUC (multi-user chat) room server on conference.example.com: +--Component "conference.example.com" "muc" +Component "conference.jabber.n39.eu" "muc" + +-- Set up a SOCKS5 bytestream proxy for server-proxied file transfers: +--Component "proxy.example.com" "proxy65" + +---Set up an external component (default component port is 5347) +--Component "gateway.example.com" +-- component_secret = "password" + +-- alex: service discovery +disco_items = { + { "conference.jabber.n39.eu", "The Netz39 Multi-User-Chat" }; +} diff --git a/templates/prosody/localhost.cfg.lua.j2 b/templates/prosody/localhost.cfg.lua.j2 new file mode 100644 index 0000000..38a6655 --- /dev/null +++ b/templates/prosody/localhost.cfg.lua.j2 @@ -0,0 +1,5 @@ +-- Section for localhost + +-- This allows clients to connect to localhost. No harm in it. +VirtualHost "localhost" + diff --git a/templates/prosody/prosody.cfg.lua.j2 b/templates/prosody/prosody.cfg.lua.j2 new file mode 100644 index 0000000..59a2521 --- /dev/null +++ b/templates/prosody/prosody.cfg.lua.j2 @@ -0,0 +1,227 @@ +-- Prosody Example Configuration File +-- +-- Information on configuring Prosody can be found on our +-- website at http://prosody.im/doc/configure +-- +-- Tip: You can check that the syntax of this file is correct +-- when you have finished by running: luac -p prosody.cfg.lua +-- If there are any errors, it will let you know what and where +-- they are, otherwise it will keep quiet. +-- +-- The only thing left to do is rename this file to remove the .dist ending, and fill in the +-- blanks. Good luck, and happy Jabbering! + + +---------- Server-wide settings ---------- +-- Settings in this section apply to the whole server and are the default settings +-- for any virtual hosts + +-- This is a (by default, empty) list of accounts that are admins +-- for the server. Note that you must create the accounts separately +-- (see http://prosody.im/doc/creating_accounts for info) +-- Example: admins = { "user1@example.com", "user2@example.net" } +admins = { "alex@jabber.n39.eu", "tux@jabber.n39.eu" } + +-- Enable use of libevent for better performance under high load +-- For more information see: http://prosody.im/doc/libevent +use_libevent = true; + +-- This is the list of modules Prosody will load on startup. +-- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too. +-- Documentation on modules can be found at: http://prosody.im/doc/modules +modules_enabled = { + + -- Generally required + "roster"; -- Allow users to have a roster. Recommended ;) + "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in. + "tls"; -- Add support for secure TLS on c2s/s2s connections + "dialback"; -- s2s dialback support + "disco"; -- Service discovery + + -- Not essential, but recommended + "private"; -- Private XML storage (for room bookmarks, etc.) + "vcard"; -- Allow users to set vCards + + -- These are commented by default as they have a performance impact + "privacy"; -- Support privacy lists + "compression"; -- Stream compression (Debian: requires lua-zlib module to work) + + -- Nice to have + "version"; -- Replies to server version requests + "uptime"; -- Report how long server has been running + "time"; -- Let others know the time here on this server + "ping"; -- Replies to XMPP pings with pongs + "pep"; -- Enables users to publish their mood, activity, playing music and more + "register"; -- Allow users to register on this server using a client and change passwords + + -- Admin interfaces + "admin_adhoc"; -- Allows administration via an XMPP client that supports ad-hoc commands + "admin_telnet"; -- Opens telnet console interface on localhost port 5582 + + -- HTTP modules + --"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP" + --"http_files"; -- Serve static files from a directory over HTTP + + -- Other specific functionality + "posix"; -- POSIX functionality, sends server to background, enables syslog, etc. + --"groups"; -- Shared roster support + "announce"; -- Send announcement to all online users + --"welcome"; -- Welcome users who register accounts + "watchregistrations"; -- Alert admins of registrations + --"motd"; -- Send a message to users when they log in + --"legacyauth"; -- Legacy authentication. Only used by some old clients and bots. + + -- alex + "smacks"; -- XEP-0198: Stream Management + "carbons"; -- XEP-0280: Message Carbons + + "csi"; -- XEP-0352: Client State Indication + "csi_compat"; + "throttle_presence"; + --"filter_chatstates"; -- triggers https://prosody.im/issues/issue/648 pre 0.9.11 + "graceful_shutdown"; + "blocking"; -- XEP-0191: Simple Communications Blocking +}; + +-- These modules are auto-loaded, but should you want +-- to disable them then uncomment them here: +modules_disabled = { + -- "offline"; -- Store offline messages + -- "c2s"; -- Handle client connections + -- "s2s"; -- Handle server-to-server connections +}; + +-- Disable account creation by default, for security +-- For more information see http://prosody.im/doc/creating_accounts +allow_registration = false; +registration_blacklist = { "127.0.0.1" }; +min_seconds_between_registrations = 3600; -- Clients must wait 1 hour before they can register another account + +-- Debian: +-- send the server to background. +-- +daemonize = true; + +-- Debian: +-- Please, don't change this option since /var/run/prosody/ +-- is one of the few directories Prosody is allowed to write to +-- +pidfile = "/var/run/prosody/prosody.pid"; + +-- These are the SSL/TLS-related settings. If you don't want +-- to use SSL/TLS, you may comment or remove this +ssl = { + key = "/etc/prosody/certs/localhost.key"; + certificate = "/etc/prosody/certs/localhost.crt"; + dhparam = "/etc/prosody/certs/dh-2048.pem"; + -- TODO for post 0.10 see http://prosody.im/doc/advanced_ssl_config again + options = { "no_sslv2", "no_sslv3", "no_ticket", "no_compression", "cipher_server_preference", "single_dh_use", "single_ecdh_use" }; +} + +-- Force clients to use encrypted connections? This option will +-- prevent clients from authenticating unless they are using encryption. + +c2s_require_encryption = true + +-- Force certificate authentication for server-to-server connections? +-- This provides ideal security, but requires servers you communicate +-- with to support encryption AND present valid, trusted certificates. +-- NOTE: Your version of LuaSec must support certificate verification! +-- For more information see http://prosody.im/doc/s2s#security + +s2s_secure_auth = false + +-- Many servers don't support encryption or have invalid or self-signed +-- certificates. You can list domains here that will not be required to +-- authenticate using certificates. They will be authenticated using DNS. + +--s2s_insecure_domains = { "gmail.com" } + +-- Even if you leave s2s_secure_auth disabled, you can still require valid +-- certificates for some domains by specifying a list here. + +--s2s_secure_domains = { "jabber.org" } + +-- Select the authentication backend to use. The 'internal' providers +-- use Prosody's configured data storage to store the authentication data. +-- To allow Prosody to offer secure authentication mechanisms to clients, the +-- default provider stores passwords in plaintext. If you do not trust your +-- server please see http://prosody.im/doc/modules/mod_auth_internal_hashed +-- for information about using the hashed backend. + +authentication = "internal_hashed" + +-- Select the storage backend to use. By default Prosody uses flat files +-- in its configured data directory, but it also supports more backends +-- through modules. An "sql" backend is included by default, but requires +-- additional dependencies. See http://prosody.im/doc/storage for more info. + +storage = "sql" -- Default is "internal" (Debian: "sql" requires one of the +-- lua-dbi-sqlite3, lua-dbi-mysql or lua-dbi-postgresql packages to work) + +-- For the "sql" backend, you can uncomment *one* of the below to configure: +sql = { driver = "SQLite3", database = "prosody.sqlite" } -- Default. 'database' is the filename. +--sql = { driver = "MySQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" } +--sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" } + +-- Logging configuration +-- For advanced logging see http://prosody.im/doc/logging +-- +-- Debian: +-- Logs info and higher to /var/log +-- Logs errors to syslog also +log = { + -- Log files (change 'info' to 'debug' for debug logs): + info = "/var/log/prosody/prosody.log"; + error = "/var/log/prosody/prosody.err"; + -- Syslog: + { levels = { "error" }; to = "syslog"; }; +} + +-- alex: security stuff, see +-- http://blog.prosody.im/mandatory-encryption-on-xmpp-starts-today/ +-- http://wiki.xmpp.org/web/Securing_XMPP and http://xmpp.net/ +s2s_require_encryption = true + +----------- Virtual hosts ----------- +-- You need to add a VirtualHost entry for each domain you wish Prosody to serve. +-- Settings under each VirtualHost entry apply *only* to that host. + +VirtualHost "example.com" + enabled = false -- Remove this line to enable this host + + -- Assign this host a certificate for TLS, otherwise it would use the one + -- set in the global section (if any). + -- Note that old-style SSL on port 5223 only supports one certificate, and will always + -- use the global one. + ssl = { + key = "/etc/prosody/certs/example.com.key"; + certificate = "/etc/prosody/certs/example.com.crt"; + } + +------ Components ------ +-- You can specify components to add hosts that provide special services, +-- like multi-user conferences, and transports. +-- For more information on components, see http://prosody.im/doc/components + +---Set up a MUC (multi-user chat) room server on conference.example.com: +--Component "conference.example.com" "muc" + +-- Set up a SOCKS5 bytestream proxy for server-proxied file transfers: +--Component "proxy.example.com" "proxy65" + +---Set up an external component (default component port is 5347) +-- +-- External components allow adding various services, such as gateways/ +-- transports to other networks like ICQ, MSN and Yahoo. For more info +-- see: http://prosody.im/doc/components#adding_an_external_component +-- +--Component "gateway.example.com" +-- component_secret = "password" + +------ Additional config files ------ +-- For organizational purposes you may prefer to add VirtualHost and +-- Component definitions in their own config files. This line includes +-- all config files in /etc/prosody/conf.d/ + +Include "conf.d/*.cfg.lua"