Skip to content

feat(curve): one STF_ZMQ_CURVE_CLIENT_KEY_<HOST> variable per device host - #276

Open
azarouski wants to merge 2 commits into
developfrom
feat/curve-client-key-vars
Open

azarouski wants to merge 2 commits into
developfrom
feat/curve-client-key-vars

Conversation

@azarouski

Copy link
Copy Markdown
Contributor
  • Documents STF_ZMQ_CURVE_CLIENT_KEY_<HOST>=<key>, one line per device host (needs feat(zmq): allow one client key per STF_ZMQ_CURVE_CLIENT_KEY_<HOST> variable stf#1114), STF_ZMQ_CURVE_CLIENT_KEYS kept for compatibility.
  • ./zebrunner.sh setup keeps the variables added to variables.env (the per-host keys were lost on a new setup).
  • README: Device hosts in a private network (STF_PROVIDER_HOST = LAN address of the agent + AGENT_HOSTS; NAT hairpin failure: registration 500 "not reachable from the hub", gray screens) and the Troubleshooting rows.

TAG_STF needs the STF release with the per-host variables. Tests: make lint, make test.

azarouski and others added 2 commits November 9, 2026 13:45
…host

The public key of every device host is its own line STF_ZMQ_CURVE_CLIENT_KEY_<HOST>=<key> of variables.env, which
the STF units get with env_file; STF_ZMQ_CURVE_CLIENT_KEYS stays for compatibility. ./zebrunner.sh setup adds the
variables added to variables.env again, as README.md describes, so the keys of the device hosts are kept.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant