releases and updates
what changed, when, and why. also available as rss.
notes
cooperative client key-memory results
all 360 registered observations evaluated. exact c25519 key bytes remained observable after close under all; gost post-close zeros do not prove erasure.
readactive timing-mark results
the historical c25519 series completed 960 executions. the primary endpoint combines a correct declaration and original-circuit responsiveness; at 75 ms every original circuit closed.
readmutual authentication between relays
relay links use kk against verified roster keys; clients use nk to authenticate the entry. both handshake flights have the same fixed size as transport frames.
reada client container with one or two volumes
the client now has a container, one file of a constant size, written once, with one or two volumes under their own passwords. the file holds no key, but with the password of a volume it reproduces the identity key and the fetch capability. the running client does not use it yet.
readnode identity bound into the keys, two mirror fixes published
with node authentication on, the identity of a node now takes part in the keys of its setup and its links, the client checks every bundle of a mirror on its own, and two security advisories about the descriptor mirror are fixed and published.
readtwo clients talk end to end through a mailbox
the testbed now runs two clients that talk under an end-to-end layer, a kk handshake and a hash ratchet, through a mailbox on the last node of their chains. the mailbox holds records it cannot read, and offline deniability is shown by a forgery.
readkeys bound to the transcript, the suite and the scheme version
every secret and every key now depends on the transcript of its exchange, on the suite and on the scheme version. two sides that differ in one byte of the transcript get different keys, and the handshake or the setup fails.
readthe second film
a film for v0.2.0. it starts where the first one said three relays, shows what the release added, and puts the measured numbers on screen, with what they cost.
readv0.2.0: the series measured again, and docs that say only what the code does
the second release gathers node authentication, authenticated links, onion key rotation and the drawn chain. its numbers were measured again on its own code, and every statement in the documentation was checked against that code.
readonion key rotation and a chain drawn at random
a relay now replaces its onion key on a timer and releases the old one, and the client draws its chain at random from the nodes it lists, five relays on the testbed.
readauthenticated links between nodes and a descriptor mirror
a relay now extends a circuit only to a node of its roster, over a link authenticated to that node, and the client takes the bundles of its chain from its entry alone.
readnode authentication and a hardening round
the client now checks node keys against a ca anchor, and relays refuse replayed setup cells, keep cell counters strictly in turn and bound what one address can take.
readjimichi.org
the project has a home, a film, and a page that says plainly what it does not protect.
readrelay clocks and a second suite
relays can now send on their own clocks, and the gost suite runs behind the same interface as the default one.
read