File

tools/build-env/Containerfile @ 13587:fdb2e0568cf8

mod_authz_internal: Make 'prosody:guest' default role for all unknown JIDs This fixes an issue where e.g. remote users or even other users on the server were unable to list MUC rooms. We want to define a permission to list MUC rooms, but we want it to be available to everyone by default (the traditional behaviour). prosody:guest is the lowest role we have. I ran a quick check and it isn't really used for anything right now that would be concerning. It was originally designed for anonymous logins. I think it's safe to treat remote JIDs as equivalent, since we have no trust relationship with anonymous users either.
author Matthew Wild <mwild1@gmail.com>
date Tue, 07 Jan 2025 14:41:32 +0000
parent 13323:7bfd6db52528
line wrap: on
line source

ARG os
ARG dist
FROM ${os:-debian}:${dist:-sid}
ENV DEBIAN_FRONTEND noninteractive
RUN set -ex; \
	apt-get update; \
	apt-get install -y --no-install-recommends \
	ccache dh-lua libicu-dev libidn11-dev libssl-dev \
	lua-bitop lua-dbi-mysql lua-dbi-postgresql lua-dbi-sqlite3 \
	lua-event lua-expat lua-filesystem lua-ldap lua-sec lua-socket \
	luarocks shellcheck mercurial; \
	apt-get install -y ca-certificates dns-root-data; \
	apt-get install -y lua-bit32 || true; \
	apt-get install -y lua-busted || true; \
	apt-get install -y lua-check || true; \
	apt-get install -y lua-readline || true; \
	apt-get install -y lua-unbound || true; \
	update-alternatives --set lua-interpreter /usr/bin/lua5.4 || true \
	apt-get clean

# Place this file in an empty directory and build the image with
# podman build . -t prosody.im/build-env
#
# Substituting podman for docker should work, where that is what's available.
#
# Then in a source directory, run:
# podman run -it --rm -v "$PWD:$PWD" -w "$PWD" --entrypoint /bin/bash \
#            --userns=keep-id --network host prosody.im/build-env
#
# In the resulting environment everything required to compile and run prosody
# is available, so e.g. `./configure; make; ./prosody` should Just Work!