Skip to content

v0.1.16

Choose a tag to compare

@github-actions github-actions released this 15 Nov 04:26
· 68 commits to master since this release
v0.1.16
639000d

ClipSync v0.1.16

Security fixes for pairing encryption and self-hosted relay defaults.

Security fixes

  • Separate the AES-GCM nonces used by the two pairing participants. Earlier
    versions encrypted both device-binding messages with the same session key
    and nonce. The new sender roles use separate nonce domains that also avoid
    the legacy sender nonce. The v1 message format and receiver behavior remain
    compatible; regression tests cover both directions of the legacy/new wire
    exchange and observe actual two-device pairing.
  • Remove the shared example token-signing key from Docker Compose. An unset,
    empty, or whitespace-only token key now generates a fresh 32-byte key from
    the operating system's secure random generator. Explicit nonblank relay keys
    shorter than 32 bytes prevent startup without exposing their value.

Upgrade impact

Upgrade both clients, then create a fresh pairing to replace keys established
by an earlier pairing. On each client run clipsync room leave --yes; create
a new room on one client and join its new code on the other. Updating a binary
does not retroactively protect an earlier handshake or replace its room keys.

Self-hosted relay operators should rebuild from this version. Remove any
example/shared token key or replace it with a privately generated value, then
restart and pair clients again. An explicitly configured short key is now
rejected. A persistent key is used as UTF-8 bytes without hex decoding; see
token-key configuration and rotation.

CLI archives include signed provenance bundles as introduced in v0.1.15.
Verify the downloaded archive
before installing it. Windows users can install the version explicitly with
scripts/install-windows.ps1 -Version 0.1.16 from this tag's checkout; the
checked-in winget manifests target an older release.

Source builds continue to require Rust 1.88 or newer. The six upstream
maintenance advisories remain visible and are tracked in the
security review.

Changes since v0.1.15