The Admin Socket Is a Privileged Interface
@Walrus 🦭/acc A lot of “key management” failures are really permission failures. Walrus storage nodes expose a local administration socket for operations like creating database checkpoints, and the docs are blunt: operations sent to that socket execute directly on the running node. That’s an administrative backdoor if you get file permissions wrong. Keep the socket path local, keep ownership tight to the walrus service user, and be wary of automation that runs as root and “helpfully” widens access. Backups deserve the same care. Full database copies are big enough to tempt sloppy handling, but they still contain the operational state of your node. Store them on a separate volume, and restore using the supported tooling instead of copying directories around.