mixandClaude Opus 5.5
dd950364a3
Security audit 2026-10-17, finding I3 (low), stage 4. No compose file set pids_limit: a fork bomb from a compromised panel or postfix had the host's pid space as its limit. Now 1024 for SelfPost - the plan said 512, but Postfix starts up to default_process_limit (100) processes per service, and a busy server runs three smtpd services, cleanup and smtp at once - 256 for nginx, Caddy, Traefik and rspamd, 64 for certbot. The comment that said root runs "very briefly" now says which root processes stay. e2e: checkPidsLimit reads /sys/fs/cgroup/pids.max in the container. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
78 lines
3.6 KiB
YAML
78 lines
3.6 KiB
YAML
|
|
# Alternative reverse-proxy: nginx. PEM files land on the host exactly like the
|
|
# Apache+certbot scenario — nginx and certbot are close cousins here, both
|
|
# writing/reading plain PEM under /etc/letsencrypt.
|
|
#
|
|
# This is a FRAGMENT, not a full replacement for ../docker-compose.yml: it
|
|
# adds an nginx + certbot pair and removes the panel's host port publish (nginx
|
|
# takes over 80/443 and proxies to the panel over the compose network
|
|
# instead). Merge it with the base file — run this from the deploy/ directory
|
|
# (Compose resolves every relative path in both files against the directory of
|
|
# the FIRST -f file, i.e. deploy/, which is why paths below are ./nginx/... -
|
|
# docs.docker.com/compose/how-tos/multiple-compose-files/merge/: "Paths are
|
|
# evaluated relative to the base file"):
|
|
#
|
|
# docker compose -f docker-compose.yml -f nginx/docker-compose.nginx.yml up -d
|
|
#
|
|
# First-run certificate issuance, before nginx has a certificate to serve -
|
|
# run once, with port 80 free (certbot answers the challenge itself;
|
|
# --webroot would need nginx already serving /.well-known). --entrypoint is
|
|
# needed: the service's own entrypoint is the renewal loop below, an
|
|
# `sh -c` that ignores any arguments given to `run`
|
|
# (docs.docker.com/reference/compose-file/services/#entrypoint; assumptions
|
|
# D-guide:301):
|
|
# docker compose -f docker-compose.yml -f nginx/docker-compose.nginx.yml \
|
|
# run --rm -p 80:80 --entrypoint certbot certbot certonly --standalone \
|
|
# -d mail.example.com --email you@example.com --agree-tos --no-eff-email
|
|
|
|
services:
|
|
selfpost:
|
|
ports: !override
|
|
- "465:465"
|
|
- "587:587"
|
|
- "25:25"
|
|
# No host publish for 8080 here: nginx reaches it over the compose
|
|
# network at selfpost:8080 instead (see nginx.conf.example).
|
|
volumes: !override
|
|
- ./data:/data
|
|
- .:/selfpost-deploy:ro
|
|
# certs/ holds two links, fullchain.pem and privkey.pem, to
|
|
# /etc/letsencrypt/live/mail.example.com/ - a path inside the
|
|
# container: certbot's directory below is mounted there whole, because
|
|
# its live/ files are relative links into archive/ (mounting live/ alone
|
|
# left them pointing at nothing). docs/guide.md, "Reverse proxy", nginx.
|
|
- ./certs:/etc/postfix/tls:ro
|
|
- ./nginx/certbot-etc:/etc/letsencrypt:ro
|
|
|
|
nginx:
|
|
image: nginx:1.27
|
|
restart: unless-stopped
|
|
# A ceiling on processes and threads (security audit 2026-10-17, I3).
|
|
pids_limit: 256
|
|
depends_on:
|
|
- selfpost
|
|
ports:
|
|
- "80:80"
|
|
- "443:443"
|
|
volumes:
|
|
- ./nginx/nginx.conf.example:/etc/nginx/conf.d/selfpost.conf:ro
|
|
- ./nginx/certbot-etc:/etc/letsencrypt:ro
|
|
- ./nginx/certbot-www:/var/www/certbot:ro
|
|
|
|
certbot:
|
|
image: certbot/certbot:latest
|
|
pids_limit: 64
|
|
volumes:
|
|
- ./nginx/certbot-etc:/etc/letsencrypt
|
|
- ./nginx/certbot-www:/var/www/certbot
|
|
# Renewal twice a day is certbot's own recommended cadence; it no-ops
|
|
# until a certificate is within its renewal window.
|
|
# (eff-certbot.readthedocs.io, User Guide, "Automated Renewals": the
|
|
# sample cron runs "certbot renew" at 0 and 12 h; renew acts only on a
|
|
# certificate near expiry.) The first certificate was issued --standalone
|
|
# (see the top of this file), and certbot renews with the plugin it was
|
|
# issued with "unless you specify other plugins or options" (same page,
|
|
# "Renewing certificates") - by then nginx holds port 80 and serves the
|
|
# webroot, so renewal names it; a renewal that succeeds with it saves it.
|
|
entrypoint: sh -c 'trap exit TERM; while :; do certbot renew --webroot -w /var/www/certbot; sleep 12h & wait $${!}; done'
|