@hydra-acp/cli 0.1.179 → 0.1.180
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/dist/cli.js +404 -393
- package/dist/daemon.js +95 -93
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -939,6 +939,8 @@ The daemon exposes a process-management surface. Treat the service token like an
|
|
|
939
939
|
|
|
940
940
|
The service token (stored at `~/.hydra-acp/auth-token`, mode 0600) is generated on `hydra-acp init` and required as `Authorization: Bearer <token>` for every REST call and as a WebSocket subprotocol or query parameter for `wss://.../acp`. The token never leaves `~/.hydra-acp/`.
|
|
941
941
|
|
|
942
|
+
> **Windows:** mode 0600 is not enforcement there. Windows derives file access from ACLs, and Node's `chmod` only toggles the read-only bit, so `auth-token` (along with `config.json`, `peers.json`, `remotes.json`, and the session records) inherits whatever the parent directory grants. On a machine with more than one interactive user, restrict `%USERPROFILE%\.hydra-acp` yourself, e.g. `icacls "%USERPROFILE%\.hydra-acp" /inheritance:r /grant:r "%USERNAME%:(OI)(CI)F"`.
|
|
943
|
+
|
|
942
944
|
For remote access (binding to a non-loopback address), enable TLS via:
|
|
943
945
|
|
|
944
946
|
```json
|