document the unauthenticated endpoints, drop TODO.md for issues
Nothing on the proxy is authenticated, so whoever can reach the port can spend the user's PPQ.AI balance — true of every version, and not something either doc said. Enabling PPQ_DATA_DIR adds a second unauthenticated route, POST /setup/api-key, which replaces the stored key (upstream PayPerQ/ppq-private-mode-proxy#23). README states both and whose each is; instructions.md tells the user plainly to expose the interface only to people they trust, which is the part they can act on. TODO.md is deleted rather than emptied. Its live-inference item is closed — PayPerQ confirmed billed end-to-end against glm-5-2 and llama3-3-70b — and the other two are now issues #2 (backup/restore, unverified: it needs the server password, and the 0.4 file split gives it two new ways to fail) and #3 (bump when the auth patch lands, and retract the warnings it makes false). The scaffold's worklist has been worked; a file left behind to say so is not worth reading.
This commit is contained in:
3 files changed
+17
-8
No files matched your search
@@ -107,6 +107,16 @@ Two interfaces on one HTTP host, port 8787, both served by the proxy:
|
||||
|
||||
Availability on LAN/Tor is decided by the user from the interface panel.
|
||||
|
||||
**No endpoint is authenticated.** Upstream ships no auth on any route, so
|
||||
whoever can reach the port can spend the user's PPQ.AI balance via
|
||||
`/v1/chat/completions`, and — because this package sets `PPQ_DATA_DIR` — can
|
||||
also replace the stored key via `POST /setup/api-key`
|
||||
([upstream #23](https://github.com/PayPerQ/ppq-private-mode-proxy/issues/23)).
|
||||
The billing exposure predates that endpoint and is inherent to the proxy; the
|
||||
key-replacement one is enabled by our `PPQ_DATA_DIR` choice, and closes when
|
||||
upstream's patch lands and this package bumps to it. `instructions.md` warns
|
||||
the user to expose the interface accordingly.
|
||||
|
||||
## Actions (StartOS UI)
|
||||
|
||||
- **Configure PPQ API Key** (`configure-api-key`) — visible and enabled at any
|
||||
|
||||
Reference in new issue
Block a user