316d653d3e
We run containers as a non-root user (no effective capabilities). Still, if a setuid binary is available in a container image, it could potentially be used to give the user the default capabilities that the container was started with. For Docker, the default set currently is: - "CAP_CHOWN" - "CAP_DAC_OVERRIDE" - "CAP_FSETID" - "CAP_FOWNER" - "CAP_MKNOD" - "CAP_NET_RAW" - "CAP_SETGID" - "CAP_SETUID" - "CAP_SETFCAP" - "CAP_SETPCAP" - "CAP_NET_BIND_SERVICE" - "CAP_SYS_CHROOT" - "CAP_KILL" - "CAP_AUDIT_WRITE" We'd rather prevent such a potential escalation by dropping ALL capabilities. The problem is nicely explained here: https://github.com/projectatomic/atomic-site/issues/203
29 lines
918 B
Django/Jinja
29 lines
918 B
Django/Jinja
[Unit]
|
|
Description=Matrix Coturn server
|
|
{% for service in matrix_coturn_systemd_required_services_list %}
|
|
Requires={{ service }}
|
|
After={{ service }}
|
|
{% endfor %}
|
|
|
|
[Service]
|
|
Type=simple
|
|
ExecStartPre=-/usr/bin/docker kill matrix-coturn
|
|
ExecStartPre=-/usr/bin/docker rm matrix-coturn
|
|
ExecStart=/usr/bin/docker run --rm --name matrix-coturn \
|
|
--log-driver=none \
|
|
--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
|
|
--cap-drop=ALL \
|
|
-p 3478:3478 \
|
|
-p 3478:3478/udp \
|
|
-p {{ matrix_coturn_turn_udp_min_port }}-{{ matrix_coturn_turn_udp_max_port }}:{{ matrix_coturn_turn_udp_min_port }}-{{ matrix_coturn_turn_udp_max_port }}/udp \
|
|
-v {{ matrix_coturn_config_path }}:/turnserver.conf:ro \
|
|
{{ matrix_coturn_docker_image }} \
|
|
-c /turnserver.conf
|
|
ExecStop=-/usr/bin/docker kill matrix-coturn
|
|
ExecStop=-/usr/bin/docker rm matrix-coturn
|
|
Restart=always
|
|
RestartSec=30
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|