Skip to content

v0.1.3

Choose a tag to compare

@malisetti malisetti released this 20 Nov 09:49
· 30 commits to main since this release

These change what scripts see; v1.0 keeps them.

  • dial takes no relay flag. --relay and --relay-http were
    ignored by dial (the address names its relay); now each is a usage
    error (exit 1) that says so. $NFLTR_PIPE_RELAY stays listen's only:
    dial ignores it.

  • --relay-pin is now --relay-cert-sha256, the name of its
    variable $NFLTR_RELAY_CERT_SHA256 and of nfltr's config set-relay --cert-sha256.

  • --direct takes on or off only; true, false and an empty
    value are usage errors.

  • listen -h and dial -h exit 0, as help does.

  • nfltr-pipe version (and --version) prints the release, its
    commit and the Go version.

  • dial --address-file - reads the address from stdin's first line
    and pipes the rest, so the address stays off the command line, which
    other users of a shared machine can see.

  • The exit table is now nfltr-send's too: one table, the relay SDK's.

  • A second dial of an address in use exits 6, not 10. The second
    dial could read the listener's reset as a refused secret (exit 10,
    e2ee_client_refused); it now exits 6 (reset), as the exit table says
    (relay client, nf1; defect 3).

  • Relayed, an end exits 0 only when its peer has the whole stream. A
    relayed close returned once the relay had the last bytes, so when the
    peer's link dropped right then an end could exit 0 while its peer exited
    6 with a prefix. A relayed close now waits for the peer to acknowledge
    the end through the relay, as a direct close does, and gives up when the
    peer stays silent past its bound: that end then exits 6 (link v0.12.20,
    relay client v0.23.10, relay-core v0.16.9;
    defect 4).

  • The contract of a 1.x release: docs/v1-contract.md
    lists the commands, flags, environment variables, exit codes, the
    address format and the compatibility rule; a test fails when the code
    and it differ.

  • make cross-version: the previous release, downloaded from GitHub
    and verified, against this checkout, both ways, relayed and direct, on
    a private relay; a check workflow job.

  • The README names the pin flag's variable right: $NFLTR_RELAY_CERT_SHA256
    (it said $NFLTR_RELAY_PIN, which nothing reads).

  • Built on link v0.12.20, relay client v0.23.10, relay proto v0.21.4 and
    relay-core v0.16.9.