From e4331d13f313f439aff9cef1ea221c8adeeebb3a Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 2 Nov 2026 22:46:48 +0100 Subject: api: allow listening to Unix sockets --- docs/trust.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'docs/trust.md') diff --git a/docs/trust.md b/docs/trust.md index dc80045..165fc9b 100644 --- a/docs/trust.md +++ b/docs/trust.md @@ -36,8 +36,10 @@ it creates is). **The HTTP API.** Every endpoint but the API description needs a user from `--htpasswd`, or one a reverse proxy names (`--user-header`): the node believes that header from `--trusted-proxies` alone, but from those blindly, so whoever can send -requests from such an address (another user of the same host, with the default -loopback addresses) can be any user. It listens on `127.0.0.1:3000` by default (`--bind-addr`) and speaks +requests from there can be any user. With the default loopback addresses, that is every +user of the host; with only the API's Unix socket (`--trusted-proxies unix`), those its +file's permissions let in: the node's user and group ([`operations.md`](operations.md), Behind a +reverse proxy). It listens on `127.0.0.1:3000` by default (`--bind-addr`) and speaks plain HTTP: to expose it, put a TLS proxy in front. All users may read and write user data and use the admin endpoints (remakes, forgetting peers, exports, log filters). There are no read-only users: whoever may open the dashboard may also edit and delete -- cgit v1.3.1