Skip to content

docs(bootstrap): set MURMUR_TOKEN via stdin, not --body (#43)#91

Open
viktor-shcherb wants to merge 1 commit intomainfrom
fix/43-bootstrap-token-stdin
Open

docs(bootstrap): set MURMUR_TOKEN via stdin, not --body (#43)#91
viktor-shcherb wants to merge 1 commit intomainfrom
fix/43-bootstrap-token-stdin

Conversation

@viktor-shcherb
Copy link
Copy Markdown
Member

Summary

Closes #43 — `docs/bootstrap.md` step 6 leaked `MURMUR_TOKEN` on
argv via `gh secret set --body "$(openssl rand -hex 32)"`. Replace
with the stdin pattern (`< <(printf '%s' "$VAR")`) used elsewhere
in the same block + flagged in `docs/cloudflare-tunnel.md` (PR #41).

The `--body` form puts the secret on argv → visible to anyone with
`ps` access for the lifetime of the gh invocation, and persisted in
shell history when the line is recalled.

Add an inline note marking `--body` as forbidden so future copy/paste
doesn't regress.

Test plan

  • `grep -rn 'secret set.*--body' docs/` returns zero hits

🤖 Generated with Claude Code

`docs/bootstrap.md` step 6 had:

  gh secret set MURMUR_TOKEN ... --body "$(openssl rand -hex 32)"

The `--body "..."` form puts the secret on argv, visible to anyone
with `ps` access for the lifetime of the gh invocation, and persisted
in shell history when the line is recalled. The neighbouring
CLOUDFLARE_TUNNEL_TOKEN line correctly uses stdin via
`< <(printf '%s' ...)`; docs/cloudflare-tunnel.md (PR #41) explicitly
flagged the --body anti-pattern.

Replace with the stdin pattern: bind to a local var, feed via
process substitution, unset. Add an inline note marking --body as
forbidden so future copy/paste doesn't regress.

Closes #43.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
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.

bootstrap.md step 6 leaks MURMUR_TOKEN on argv via gh secret set --body

1 participant