LibreTime's Public Schedule and Its API Control Plane Need Separate Inventories
LibreTime runs a radio station's schedule, media, playout, and web administration. Some endpoints are designed to share the current or upcoming show with a public website. Others carry internal automation authority. A product-title count cannot tell those paths apart.
The ZoomEye SDK probe on 22 November 2026 used sub_type=all, page 1, and pagesize=1. app="LibreTime" returned 0 matches and title="LibreTime" returned 776. The probes ran between 06:46 and 06:47 Asia/Shanghai.
The zero application result and 776 title result are index observations, not a census. The product may expose a login page, a public player, a reverse-proxy error, or an API route. Each requires confirmation before it belongs in an asset inventory.
The documented public boundary
LibreTime's API documentation says that across a public network, API requests should use HTTPS and the web server should accept requests to the api/ directory only from specific hostnames or IP addresses. The user settings documentation identifies live and upcoming show metadata as publicly retrievable when the public API option is enabled. Those are deliberate read-only outputs.
The configuration includes an internal API authentication key. That key belongs to the automation and control path, not to the listener-facing schedule. A reverse-proxy rule that exposes the entire API tree to the internet because the public schedule is useful has blurred the two roles.
Inventory the paths
For each owned LibreTime host, record the web UI, public API, internal API, playout services, database, and reverse-proxy rules. Capture which endpoints are anonymous, which use the internal key, and which require a user session.
Put the administrative UI and internal API on a private network. Publish only the specific schedule endpoints that a public website needs, and restrict their source networks where practical. Terminate TLS at a trusted proxy and preserve the original client address only if the proxy overwrites untrusted headers.
Test from the public internet without credentials. The response should include only the intended public schedule, not station settings, media-management routes, or internal automation controls. Then test from the automation network with the expected key and confirm that the restriction does not break playout.
Count with a purpose
The 776 title matches provide a candidate list, not a security verdict. LibreTime's public schedule can legitimately be indexed. A useful review separates public read access from the internal API and records who owns each host.
Top comments (0)