F: correct the peers docs against the finished behaviour
docs/consolidator.md: the Testing section described the pre-feature test (no tests/peers.rs, the old tests.<system>.peers attribute, a note about assertions failing by design) and is rewritten for both layers, the module's eval check included. A shutdown subsection backs the README's promise, the agenix examples say why a consolidator would bind 0.0.0.0 (remote callers; peers need no inbound port), and the VM test asserts the chained-request status is exactly 400 as documented. README: token rotation on NixOS also needs a reload for the LoadCredential copy.
This commit is contained in:
1 parent
0a83386de5
commit
04992e202d
3 files changed
+15
-7
No files matched your search
@@ -131,7 +131,7 @@ token_file = "/etc/skyg/peer-nas.token" # 0600, owned by the service user
|
||||
allow_plain_http = true
|
||||
```
|
||||
|
||||
`token_file` holds a path, never the token. A consolidator has to replay the peer's plaintext bearer token, so the token lives in a file managed outside `slinuxm` (agenix on NixOS), is read into memory on every check and request, and never appears in the config, `--print-config`, the database or the logs. Mint **one token per consolidator on every peer** and use it only there (`sudo -u <service user> slinuxm token create consolidator-<host>`), so a single `token revoke` on a peer cuts that consolidator off and nothing else. Replacing the file is enough to rotate: no restart.
|
||||
`token_file` holds a path, never the token. A consolidator has to replay the peer's plaintext bearer token, so the token lives in a file managed outside `slinuxm` (agenix on NixOS), is read into memory on every check and request, and never appears in the config, `--print-config`, the database or the logs. Mint **one token per consolidator on every peer** and use it only there (`sudo -u <service user> slinuxm token create consolidator-<host>`), so a single `token revoke` on a peer cuts that consolidator off and nothing else. Replacing the file is enough to rotate: the next check reads the new value, and no restart is needed. On NixOS also run `systemctl reload skyg-linux-tracker` so systemd re-copies the credential the unit holds (`RefreshOnReload=credentials`).
|
||||
|
||||
Two checks per peer, kept in memory and reset on restart:
|
||||
|
||||
|
||||
Reference in new issue
Block a user