Repository navigation
v0.1.8
These change what scripts see; v1.0 keeps them.
-
Exit codes are the relay SDK's, the same as nfltr-pipe's. Exit 3
(failed) is split: 3not_found(the sender is gone), 5
unreachable(the relay or the sender not reached), 6reset(the
session cut), 7e2ee_pin_mismatch, 10e2ee_client_refused; a
refusal (a name exists, the sender busy, a commit refused) is 4
refused, no longer 2; 2 is nowauth(the relay refused the sender's
certificate, or serves no address without an account) and 9
balance_exhausted. receive--json'scodenames them so. -
A stopped sender exits 130 (SIGINT) or 143 (SIGTERM), no longer 0,
so a script tells it from a--oncesender whose transfer completed
(0). -
receivetakes no relay flag.--relayand--relay-httpwere
ignored by receive (the address names its relay); now each is a usage
error (exit 1) that says so.$NFLTR_SEND_RELAYstays send's only:
receive ignores it. -
--relay-pinis now--relay-cert-sha256, the name of its
variable$NFLTR_RELAY_CERT_SHA256and of nfltr'sconfig set-relay --cert-sha256. -
--directtakesonoroffonly;true,falseand an empty
value are usage errors. -
send -handreceive -hexit 0, ashelpdoes. -
nfltr-send version(and--version) prints the release, its
commit and the Go version. -
Protocol versions are negotiated. Every 1.x end speaks version 4;
a receiver takes any version from 4 to its own and both speak the
lower, so a later 1.x sender works with an earlier 1.x receiver. -
A relayed close waits for the other end. A relayed session's close
returned once the relay had the last bytes; it now returns once the
other end acknowledged them through the relay, as a direct close does,
and gives up when that end stays silent past its bound (link v0.12.20,
relay client v0.23.10, relay-core v0.16.9). -
A reset before the sender's answer is a reset, not a refused secret.
A receive whose session was reset before the sender answered could exit
10 (e2ee_client_refused); it now exits 6 (reset): only a sender that
refused the address's secret is exit 10 (relay client v0.23.10). -
The contract of a 1.x release: docs/v1-contract.md
lists the commands, flags, environment variables, exit codes, the
--jsonkeys, the address format, the protocol version 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 (a sender of one, a
receiver of the other), relayed and direct, on a private relay; in
the check workflow. -
Built on link v0.12.20, relay client v0.23.10, relay proto v0.21.4 and
relay-core v0.16.9.