KarasumikuraThis plugin has no README in the catalog yet.
All plugins
hermes-vault-broker
Fill saved logins from an out-of-process credential broker. The broker runs as its own system user with ProtectHome=yes, derives a KEK from a passphrase with scrypt and keeps the random data key (DEK) in checked mlock'd memory, and writes the password into the page itself over a DevTools endpoint taken ONLY from its own root-owned loopback config — the model cannot choose it, and a tab's websocket is refused unless its host:port matches. The agent sends (handle, origin) over a unix socket and gets a fill count back; SO_PEERCRED limits the gateway uid to status/list/fill while unlock/add/remove/init/lock stay with root and the broker's own uid. Exact-origin binding is re-asserted inside the tab immediately before the write. Import only accepts a JSON export the operator made themselves; the broker never opens Hermes's credential stores. An optional CDP-pipe mode lets the broker launch and own Chromium with no TCP debugging port. Linux; stdlib unittest suite; deps cryptography + websockets. Disclosure — requires running `scripts/install.sh` as root, which creates a `vaultd` system user, adds the Hermes user to its group, pip-installs `cryptography` and `websockets` into /opt/hermes-vault-broker/venv and enables a system-wide `hermes-vault-broker` systemd service; saved passwords are typed into browser pages over the Chrome DevTools endpoint configured in /etc/hermes-vault-broker/cdp.json, so any process running as the browser's user can read a filled field or take over that port; the optional unlock page (`unlock-form`) serves the passphrase form over self-signed HTTPS and the README suggests binding it to 0.0.0.0.
About
Fill saved logins from an out-of-process credential broker. The broker runs as its own system user with ProtectHome=yes, derives a KEK from a passphrase with scrypt and keeps the random data key (DEK) in checked mlock'd memory, and writes the password into the page itself over a DevTools endpoint taken ONLY from its own root-owned loopback config — the model cannot choose it, and a tab's websocket is refused unless its host:port matches. The agent sends (handle, origin) over a unix socket and gets a fill count back; SO_PEERCRED limits the gateway uid to status/list/fill while unlock/add/remove/init/lock stay with root and the broker's own uid. Exact-origin binding is re-asserted inside the tab immediately before the write. Import only accepts a JSON export the operator made themselves; the broker never opens Hermes's credential stores. An optional CDP-pipe mode lets the broker launch and own Chromium with no TCP debugging port. Linux; stdlib unittest suite; deps cryptography + websockets. Disclosure — requires running `scripts/install.sh` as root, which creates a `vaultd` system user, adds the Hermes user to its group, pip-installs `cryptography` and `websockets` into /opt/hermes-vault-broker/venv and enables a system-wide `hermes-vault-broker` systemd service; saved passwords are typed into browser pages over the Chrome DevTools endpoint configured in /etc/hermes-vault-broker/cdp.json, so any process running as the browser's user can read a filled field or take over that port; the optional unlock page (`unlock-form`) serves the passphrase form over self-signed HTTPS and the README suggests binding it to 0.0.0.0.
Developer Mode
Explore built-in Hermes toolsets and actions.
