4 ms·
At least, have it respond only to authenticated requests. Caddy supports client certificate authentication: https://caddyserver.com/docs/json/admin/remote/acce
by sergiosgc 3y ago
At least, have it respond only to authenticated requests. Caddy supports client certificate authentication:
https://caddyserver.com/docs/json/admin/remote/access_control/public_keys/ https://caddyserver.com/docs/json/admin/remote/access_contro...
- Freaky 3y agoCaddy also supports Unix sockets, which should be rather more difficult to smuggle requests to, and can be protected by file permissions: admin listen unix//var/run/caddy/admin.sock
- rekoil 3y agoThis (if they definitely must leave the functionality enabled by default) is what should be the default honestly. I still can't fathom why that isn't the case!
- oarmstrong 3y agoI would imagine so the default behaviour could be identical across platforms.
- robertlagrant 3y agoI imagine it's for Windows users. But yes, it could very sensibly be the default in Unix.
- Freaky 3y agoI'll see about getting it made the default for the FreeBSD port at least.
- francislavoie 3y agoCaddy maintainer here: we're looking to move to unix socket by default for Linux distributions. See https://github.com/caddyserver/caddy/issues/5317 https://github.com/caddyserver/caddy/issues/5317, the plan is to set this env var in the default service config but I'm trying to be careful about backwards compatibility so I haven't pushed the change for our deb package yet. Will likely do it soon.