Repository navigation
v0.1.10
- A sender whose machine was off past its certificate's life serves
again: the expired certificate is renewed before the first connection
presents it (before: the relay refused it for good andsendexited 6).
A refused machine's error is one line: no certificate dump, no relay
answer,nfltr config loginnamed once; it no longer says--relay names another. - A machine certificate renews through a pinned private relay: the
renewal trusts the relay certificate that--cert-sha256(else
$NFLTR_RELAY_CERT_SHA256) pins, as the sessions do; before, it used
the system roots only, a self-signed relay refused every renewal and
the certificate lapsed. - Direct transfers on long, lossy paths: the direct path's QUIC uses
BBR instead of NewReno (link quiclink v0.7.2). A 10 GiB direct transfer
Helsinki to Singapore (260 ms, 0.03-0.06 % loss, 29 % of packets
reordered) ran at a steady 352-359 Mbit/s; before, 36-166 Mbit/s,
falling to 15-59. The wire is unchanged. - Hole punching: the dialling end sends its first QUIC packet half a
relay round trip after the sync, once the other end's first probe has
opened its NAT (before: at the sync, and the first packet met a closed
NAT); an attempt that no candidate answered is followed by another, at
most three per round, before the transfer stays relayed; a round for a
session that has ended stops (relay client v0.24.1). - Built on link v0.13.3, relay client v0.24.1, relay proto v0.22.1 and
relay-core v0.19.1.
From the v1.0 surface review (docs/v1-surface-review.md).
These change what scripts see; v1.0 keeps them.
- receive
--json:erroris nowmessage,first_byte_sis now
first_byte_seconds, the names nfltr'scatevents and metrics use.
A script reading either key reads the new one. - SIGHUP stops the sender cleanly, exit 129: its sessions close at
once (before, the process died and its receivers waited for the link's
liveness). The shell reported 129 for that death before too. A
receive stopped by SIGHUP exits 6 and resumes, as at SIGINT. - Flags may follow the files:
nfltr-send send report.pdf --once
now sendsreport.pdfonce (before: a file named--once, exit 1).
After--every word is a file. - The module has no Go API:
xferis nowinternal/xfer. Nothing
outside this repository imported it. - The built binary
cmd/nfltr-send/nfltr-sendcommitted in v0.1.8 is
removed, and a test keeps binaries out. --relay-cert-sha256is now--cert-sha256, the namenfltr config set-relayand nfltr'scatcommands use (one name in all three tools);
--relay-cert-sha256is refused.$NFLTR_RELAY_CERT_SHA256is
unchanged.- Large files: the address and the commit come sooner. The sender's
BLAKE3 tree and the receiver's check of the file on its disk read
4 MiB at a time instead of 256 KiB; from a cold page cache that read
the disk 1.6 times as fast (local, docs/performance.md). - A file changed while a later one was sent is no longer committed as
offered. The sender checks every file's size and modification time
again before it ends the transfer (an earlier one changed: refused,
"changed since it was offered"), and the receiver checks every staged
file again before it commits (one another program wrote after it was
verified: the commit is refused, the stage kept, and the next session
sends what no longer verifies). Modelspec/Offer.tla(lane SENDMULTI).