Image runs with every capability dropped; INBUXA_LISTENER_PORTS #443

Merged
jcoffey-dev merged 1 commits from feat/no-file-caps into main 2026-11-18 15:55:44 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev 57eee17522 Image runs with every capability dropped; INBUXA_LISTENER_PORTS
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 13m7s
The binary carried cap_net_bind_service as a file capability, so exec
failed outright wherever the capability isn't in the bounding set, as in a
Kubernetes pod with every capability dropped. The images no longer set it
(or install libcap to set it).

Docker users are unaffected: Docker sets ip_unprivileged_port_start=0 in a
container's own network namespace, so the server still listens on 25, 443,
465 and 993 unprivileged. Under podman or --network host, grant the sysctl
or CAP_NET_BIND_SERVICE.

INBUXA_LISTENER_PORTS moves the default listeners a new store gets, or
leaves some out (smtp=2525,pop3s=off,...). It is checked on every start
and a mistake stops the server, but only used when the store has no
listeners yet; after that the registry holds them.

A bind refused on a port below 1024 now says what would allow it.

Closes #424
2026-11-18 07:08:14 -07:00