The agent that grows with you
Python aiai-agentai-agentsanthropicchatgptclaudeclaude-codecodexhermeshermes-agentllmnous-researchopenai
chore(catalog): review disclosure for hermes-dpapi-secrets
teknium181d65005281d
diff --git a/plugin-catalog/hermes-dpapi-secrets.yaml b/plugin-catalog/hermes-dpapi-secrets.yamlindex 4374248c8d6..6027a565bc7 100644--- a/plugin-catalog/hermes-dpapi-secrets.yaml+++ b/plugin-catalog/hermes-dpapi-secrets.yaml@@ -1,25 +1,7 @@name: hermes-dpapi-secretsrepo: https://github.com/Yicheng-Mark/hermes-dpapi-secretssha: c1651a401370013493903883d7ec4a1c90731b41-description: >-- Resolve Hermes environment variables at startup from a single secret file encrypted with- the Windows Data Protection API, instead of keeping provider keys in plaintext in .env or- auth.json. Config is secrets.dpapi.map, an ENV_VAR -> store-name mapping (bare names or- dpapi:// names) plus an optional file path (default <HERMES_HOME>/secrets.dpapi). The file- is one DPAPI blob keyed by the current Windows user profile, so it is unreadable by another- Windows account and worthless off the machine; it is written by the bundled CLI- (python -m hermes_dpapi_secrets set NAME, value read from a prompt or stdin, never from- argv) and only read at runtime. Mapped names that are missing or empty are skipped with a- warning; a file that is not ours, a blob this user cannot decrypt, or a payload that is not- a flat string map is reported as an error with nothing injected. Disclosure - this source- decrypts a file for every Hermes process that enables it: resolved values become- environment variables of the Hermes process and its children, exactly like .env entries,- so anything that can read that environment can see them. User-scope encryption only (the- machine-wide flag is never used and is not exposed), and the at-rest protection is a bar- for backups, cloud sync and dotfiles, not a boundary against code already running as the- same user. Stdlib-only (ctypes): no Python dependencies, no subprocesses, no network calls,- no self-update. Windows only. Applying fetched values stays the orchestrator's job; the- plugin never writes os.environ itself.+description: "Resolve Hermes environment variables at startup from a single secret file encrypted with the Windows Data Protection API, instead of keeping provider keys in plaintext in .env or auth.json. Config is secrets.dpapi.map, an ENV_VAR -> store-name mapping (bare names or dpapi:// names) plus an optional file path (default <HERMES_HOME>/secrets.dpapi). The file is one DPAPI blob keyed by the current Windows user profile, so it is unreadable by another Windows account and worthless off the machine; it is written by the bundled CLI (python -m hermes_dpapi_secrets set NAME, value read from a prompt or stdin, never from argv) and only read at runtime. Mapped names that are missing or empty are skipped with a warning; a file that is not ours, a blob this user cannot decrypt, or a payload that is not a flat string map is reported as an error with nothing injected. Disclosure - this source decrypts a file for every Hermes process that enables it: resolved values become environment variables of the Hermes process and its children, exactly like .env entries, so anything that can read that environment can see them. User-scope encryption only (the machine-wide flag is never used and is not exposed), and the at-rest protection is a bar for backups, cloud sync and dotfiles, not a boundary against code already running as the same user. Stdlib-only (ctypes): no Python dependencies, no subprocesses, no network calls, no self-update. Windows only. Applying fetched values stays the orchestrator's job; the plugin never writes os.environ itself. Disclosure — decrypts a DPAPI-encrypted secret file (default <HERMES_HOME>/secrets.dpapi) at startup for every Hermes process that enables it, and the resolved values become environment variables of Hermes and its child processes like `.env` entries; the encryption is per Windows user and protects backups, cloud sync and copied files, not against other code running as the same user. Local only: no network calls, no subprocesses."maintainer: Yicheng-Marktier: communitycategory: tools