mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-06 05:17:15 +00:00
18 lines
2.4 KiB
YAML
18 lines
2.4 KiB
YAML
name: secure-env-ingress
|
|
repo: https://github.com/web3blind/hermes-secure-env-plugin
|
|
sha: 8771da5ea9cdf8531ddffb891e488cc57f28bb8d
|
|
subdir: secure_env_ingress
|
|
description: "One-use HTTPS forms for missing environment secrets, native encrypted Browser Vault logins/TOTP setup keys and payment cards, retained exact-parent login/password and saved TOTP filling, protected payment-field filling, nested verification codes/passcodes and guarded indexed code groups, and approved secret operations outside chat and LLM input. Disclosure — /senv setup supplies a skill using sudo for host packages and TLS setup after approval; the TLS listener binds all interfaces by default; pre_gateway_dispatch observes gateway messages to bind commands to their sender. Interactive Telegram secret entry uses secure_env_vault; secure_login_fill consumes existing native Vault handles without registering a login backend. Browser writes require an explicitly selected existing parent and the public captured-CDP dispatch API, retain the original transport and exact document/control guards, and fail closed on reconnect, profile or human-control lease changes; tab creation ownership is not required. No native fill fallback or explicit site-form submission occurs. Payment filling requires separate native consent; explicit resume requires existing nonempty values to match Vault. Card storage includes encrypted CVC. Site input callbacks, especially 3-D Secure, may authorize or auto-submit an operation. Unknown outcomes require external verification before retry. secure_operation executes administrator-allowlisted, SHA-256-pinned external Python consumers with gateway privileges; consumers are trusted, not sandboxed, and none are enabled by default. Secret input is not persisted by this mode; consumers must enforce their own handling policy. Links are bearer authorization, not submitter identity; cancellation cannot stop an already-running consumer. Setup bootstrap reads the profile .env directly to obtain TELEGRAM_ALLOWED_USERS owner IDs."
|
|
maintainer: web3blind
|
|
tier: community
|
|
category: tools
|
|
version: "0.8.4"
|
|
requires_hermes: ">=0.22.2"
|
|
docs_url: https://github.com/web3blind/hermes-secure-env-plugin/blob/8771da5ea9cdf8531ddffb891e488cc57f28bb8d/README.md
|
|
platforms: [linux]
|
|
capabilities:
|
|
provides_tools: [secure_env_vault, secure_login_fill, secure_payment_fill, secure_operation]
|
|
provides_hooks: [pre_gateway_dispatch]
|
|
provides_middleware: []
|
|
requires_env: []
|