Repository navigation
Braid 0.3.1
Security notice — updated September 26
Do not use 0.3.1 with credentials.
Installed-package probes confirmed remaining credential-origin defects in legacy records, workspace auth selection, and model redirects.
Oversized Bearer values and quoted secret values can also leak through output sanitization.
The 0.3.2 credential correction is merged.
The overflow correction is in progress.
Version 0.3.2 is not yet published.
Its protected live release checks remain required.
Braid 0.3.1 release notes
0.3.1 is a security release.
Upgrade from 0.3.0.
Security
- Secret redaction covers quoted, escaped, and prefixed names.
0.3.0 did not redact values such as{"token":"…"},{\"api_key\":\"…\"}, orTANGLE_API_KEY=….
Those values could reach the journal and stream subscribers.
Batch and streaming redaction now use one recognizer.
Streamed text is released one complete line at a time, so a chunk boundary cannot separate a secret name from its value. - A stored credential is bound to its endpoint origin.
In 0.3.0, an edited endpoint in the workspace configuration received the existing credential.
Setup now stores the origin with the secret in the operating-system credential store.
Braid releases the secret only to that origin.
If an endpoint origin changes, run setup again to authenticate the new endpoint.
A credential stored by 0.3.0 keeps working on the default Tangle origin for its connection kind, or on a loopback CLI Bridge.
Fixed
- The README shows the
.braid/profile.jsonthat a clean workspace needs before the first run.
0.3.0 setup found no profile in a clean workspace and could only exit.
Upgrade notes
- A connection with a custom, non-loopback endpoint and a credential stored by 0.3.0 reports that it needs authentication.
Run setup for that connection once.
Published @tangle-network/braid@0.3.1 from commit d7fa68d. The exact package completed candidate and registry install/use checks on Linux x64 and macOS arm64.