Please report security issues privately to the repository owner instead of opening a public issue with exploit details, tokens, subscription URLs, node credentials, or production configuration.
- Treat profile tokens, admin tokens, upstream subscription URLs, and custom request headers as secrets.
- Prefer
Authorization: Bearer ...over query-string tokens when clients support custom headers, because query strings are commonly recorded by reverse proxies and access logs. - Terminate TLS before exposing Sub Manager outside a trusted network.
- Keep
/api/*behind an additional access-control layer for internet-facing deployments. - Never commit
config.yaml; the repository ignores it by default. - The browser admin panel sends the admin token only in the
Authorization: Bearerheader and keeps it in per-tabsessionStorage; it is intentionally not placed in the admin-page URL. /api/configis secret-bearing: authenticated responses include profile tokens, upstream URLs, and configured upstream request headers.