Johnathan Corgan
af66ffaea1
Carries the seven security fixes up from the maintenance line. Master has been refactored underneath most of the code they touch, so this merge lands only the part that applies as written; the rest is re-implemented against master's architecture in the commits that follow. Landed complete by this merge: - Bound the coordinate-cache warm path by the encrypted-header parser. The guard applies unchanged in src/node/dataplane/forwarding.rs, which is where master keeps the warm path. Its test is not here: master and the maintenance line added different tests to the same region of src/node/tests/forwarding.rs, and the union is made with the test that belongs to it. - Filter and cap the punch targets taken from a peer's traversal signal. - Reject traversal signals dated in the future. - The character-boundary fix to the session-id log helper, which is what made the two traversal fixes safe to log. Deferred to follow-on commits, because the mechanism they change does not exist upstream in the shape the fix was written against: - Bound a remote-supplied path MTU, and give the cache a way back. Master routes the keep-tighter rule through a sans-IO core with an apply site the maintenance line does not have, and keeps the lookup handlers in src/node/handlers/lookup.rs rather than a discovery module. The floor constant, the release helper and the TUN clamp side are here; the apply sites are not. - Act on a routing signal only for a destination this node has bound. - Never destroy an established session on an unauthenticated setup message. Master decides rekey in a clock-free core off a snapshot, so the fix's condition has no loop to sit in. - Let flap dampening engage again after an episode lapses. Master extracted the mechanism into a component with an injected clock. The counters, statistics and status-pane fields for the deferred fixes merged cleanly and are in this commit, so they read zero until the fix that feeds them lands. The halves that would not compile or would fail without their fix were held back with it. Green at this tree: fmt, build, clippy --all-targets -D warnings and test --lib at 1784 passed.
FIPS Documentation
FIPS (Free Internetworking Peering System) is a self-organizing encrypted mesh network built on Nostr identities, capable of operating over arbitrary transports — local networks, the public internet, Tor, Bluetooth, or point-to-point links — without central infrastructure.
With FIPS, your machine becomes a node in the mesh with a self-generated cryptographic identity. There are two ways to deploy it.
As an overlay on top of existing IP networks, FIPS lets your node reach any other FIPS node wherever it sits — behind a NAT, on a different ISP, on a phone over cellular, on a laptop with only Bluetooth in range, or behind a Tor onion. The mesh forwards IPv6 traffic transparently and end-to-end encrypted, with no central VPN concentrator or coordinating server.
From the ground up over raw Ethernet, WiFi, or Bluetooth, FIPS provides a complete permissionless network without any pre-existing IP infrastructure, ISP, or DNS. Any node that joins the link gets routable IPv6 addresses, peer discovery, and a path to every other node automatically.
Either way, existing networking software runs over it unchanged: SSH, HTTP servers, file transfer, anything IPv6-native works the same way it would on a local network.
New to FIPS? Start with the Getting Started guide.
Documentation Sections
Tutorials
If you are starting from scratch and want a guided path to a working mesh, go here.
How-To Guides
If you have a specific task in mind — enabling a feature, deploying a component, diagnosing a problem — go here.
Reference
If you need to look up wire formats, configuration keys, command flags, or counter inventories, go here.
Design
If you want to understand how the mesh self-organizes, why FIPS makes the choices it does, or how the pieces fit together, go here.