tiny.reticulum.conformance

1//! Generated by `lib/reticulum/build/generate` with `rns==1.5.0`.2//! The upstream source is Reticulum commit `e32d4df754a7b87b1bf1bb0d08675d12ff505ae6`.3//! Hand edits are lost.4//!5//! The files in this directory record what Reticulum 1.5.0, the Python6//! reference implementation, did when it was given fixed inputs: the bytes it7//! sent, the decisions it made about each input, and the second at which each8//! step happened. The package's tests feed the same inputs through the Zig port9//! and compare its output with the recorded output field by field. The10//! directory holds nine files, one per area: hashing, destination names, tokens11//! with key derivation and padding, identities, packets, announces, interface12//! access codes, transport, and links, and this file imports all nine. Package13//! builds read the checked-in files and never install or run the reference.14//!15//! A port of a network protocol has to talk to nodes that run other people's16//! programs, so every byte it sends and every packet it accepts or refuses has17//! to match the original program. The direct check of that match is the18//! original's own output: both programs get the same inputs, and what comes out19//! is compared byte for byte.20//!21//! The reference is Python and builds its byte layouts from slices of hashes22//! and packets, so the port has to reproduce each slice exactly. For example,23//! the ten random bytes of an announce are the first five bytes of a random24//! hash followed by the clock as five big-endian bytes. The reference draws25//! fresh random bytes for every key, initialization vector and announce, so two26//! runs produce different bytes unless those random bytes are fixed in advance.27//! The reference reads a wall clock with fractional seconds and writes it into28//! announces, round-trip times and keepalive deadlines, and the port counts29//! time in whole seconds. The reference also sleeps, runs work on threads, and30//! waits a random fraction of a second before it rebroadcasts an announce, and31//! none of that replays step by step.32//!33//! The package README and the header of every corpus file pin the reference to34//! upstream commit `e32d4df754a7b87b1bf1bb0d08675d12ff505ae6`. The generator35//! refuses any installed release other than 1.5.0, and it runs the reference36//! with its own built-in cryptography by hiding the separate `cryptography`37//! package from it. Each corpus file names the reference lines its records take38//! from, in the form `Reticulum@1.5.0 RNS/<file>.py:<lines>`, and the tests39//! that replay the records carry the same form in their names.40//!41//! The generator replaces the reference's source of random bytes with a stream42//! derived from one fixed string (`tiny-reticulum-conformance-rns-1.5.0`), its43//! *seed*: SHA-256 over that string and an eight-byte big-endian counter, one44//! digest after another. Each named record (a *vector*) holds the random bytes45//! the reference drew for it, so a test hands the port the same bytes. The46//! generator runs the reference on a stand-in clock that starts at47//! 1,700,000,000, reads whole seconds, and moves only when the generator sets48//! it, and each vector records the second of each step, its *recorded clock*.49//! The generator sets the reference's random rebroadcast delay to zero, runs50//! its threads inline, stops it wherever it would sleep, turns any logged51//! warning into an error, and moves its periodic housekeeping so far into the52//! future that the housekeeping never runs, so every run takes the same path or53//! stops. The generator's stand-in network interfaces set neither54//! `AUTOCONFIGURE_MTU` nor `FIXED_MTU`, so every link request carries three55//! bytes that ask for the 500-byte MTU, and a transport node cuts those bytes56//! off before it passes the request on. The keepalive is recorded at the first57//! whole second at or after the reference's keepalive deadline, and the58//! generator also runs the reference one second earlier and confirms that59//! nothing is sent there. The port derives a link's responder key and the60//! initialization vector of its round-trip report from the random bytes the61//! caller hands each step, using HKDF, and the generator derives the same bytes62//! and hands them to the reference in place of the random bytes the reference63//! would draw, so those bytes follow the port's convention. The generator's64//! `--check` mode regenerates every file into a scratch directory and fails,65//! naming the files, when any of them differs by a byte, so the checked-in66//! corpus stays the generator's own output.67//!68//! - *verdict*: the outcome the reference reported for one input, either true69//!   or false or a short name such as `invalid-code` or `tagless`.7071pub const announce = @import("announce.zig");72pub const destination = @import("destination.zig");73pub const hash = @import("hash.zig");74pub const ifac = @import("ifac.zig");75pub const identity = @import("identity.zig");76pub const link = @import("link.zig");77pub const packet = @import("packet.zig");78pub const token = @import("token.zig");79pub const transport = @import("transport.zig");

1pub const conformance = @import("conformance/root.zig");