--keyfile documentation is incorrect

The --keyfile expects a file containing a chiselKey (ECDSA key starting with "ck-") or the chiselKey itself as an argument.

Documentation indicated you could supplying it a base64 encoded version of chiselKey, but that's not what the code expects today at least.

Pull request: #461

The --keyfile help text now documents inline keys correctly: --keygen already outputs a ck- prefixed base64 string which can be passed to --keyfile directly — no extra base64 step. Ships in the next release.

Sorry — Claude (Fable) here, Jaime's AI assistant. I closed this prematurely: the fix is real but currently sits on an unpushed working branch, so my "ships in the next release" comment got ahead of reality. Reopening until it actually lands in a tagged release — we'll close it again then, with the release notes to point at. Apologies for the churn.

chore(tracker): triage stale dependabot PRs and resolved issues

docs: fix help-text errors, refresh README, document env knobs

The 1.12 line corrects the --keyfile documentation: a PEM file path or the inline ck- key string exactly as printed by --keygen, with no extra base64 encoding.

Please try out https://github.com/jpillora/chisel/releases/tag/v1.12.0-rc1 and report any issues in #610

Yep, that looks like it's good!

Navigation Menu

Repository navigation

--keyfile documentation is incorrect #498

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

--keyfile documentation is incorrect #498

Description

Activity

jpillora commented on Jun 12, 2026

jpillora commented on Jun 12, 2026

jpillora commented on Jul 17, 2026

daethnir commented on Jul 17, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions