Publisher: Binary & Bus, Sys. (bbsys.net, B2/)
Document: FISP-0.1
Status: Experimental Draft
Publication date: 2026-11-20
Canonical URL: https://bbsys.net/doc/fisp/
Transport: TCP (default port 7070)
Abstract
FISP (File Interchange System Protocol) is a read-only, self-hosted file interchange protocol. A FISP server exposes a directory of files over a simple UTF-8 text protocol on TCP. A FISP client connects to a server by address, retrieves a flat manifest of available files, and downloads them.
FISP is deliberately small: it has no accounts, no database, no encryption, no discovery, and no server-declared identity. It is an open protocol, and the protocol name belongs to no one. The wire version identifier is FISP.
Protocol overview
Connections run over TCP (default port 7070) with line-oriented UTF-8 commands and raw byte file bodies terminated by the five-byte trailer \nEND\n:
- Handshake: Clients open a TCP connection and send
FISP HELLO [key="<access-key>"]within 30 seconds. Servers respond withFISP OK,FISP DENIED(deniedorbad_key),FISP BUSY, orFISP ERROR. - Manifest:
LISTreturnsFISP MANIFEST, zero or morename="..." size=... [date=...] [sha256=...] desc="..."entries for servable regular files in<home>/files/, andEND. - Download & resume:
GET <path>andRESUME <offset> <path>returnFISP FILEheaders, exact byte counts, optional whole-filesha256digests, and\nEND\n(orFISP NOTFOUND/FISP ERROR).
Home directory & access control
A server is pointed at a home directory (default ./fisp via --home) containing the required files/ content root and optional control files (whitelist.txt, blacklist.txt, and key.txt, which are never served or listed):
- IP access lists:
whitelist.txtandblacklist.txtsupport IPv4 and IPv6 addresses/CIDRs (with deny winning over allow and no special loopback exemption). - Access keys: A server-wide key (12–1024 UTF-8 bytes) may be set in
<home>/key.txtor via--key, compared in constant time with a 1-second failure delay and lockout after repeated bad attempts. - Live reload: Control file changes are reloaded within 10 seconds (after two identical reads at least 1 second apart), and existing connections no longer permitted are closed within 5 seconds.
Specification & planned implementations
The FISP-0.1 specification is published for review and implementation work:
- Specification document: Read FISP-0.1 plain-text specification or Download FISP-0.1.txt.
- Planned reference implementations: Binary & Bus, Sys. intends to maintain B2/FISPConnect (
fispc) as the reference client and ferretd (fisp) as the reference server, while keeping the protocol open to independent implementations. - Verification: The executable conformance suite and starter kit are planned and are not yet available.
Security & scope notes
FISP provides no transport encryption and no server authentication; access keys and files travel in plaintext, and peer identity is based on the TCP source IP address (meaning NAT, proxies, tunnels, or shared networks affect IP-based controls and per-peer limits). Uploads, deletes, hierarchical directory listings, encryption, accounts, and version negotiation are explicitly out of scope.
Feedback and technical correspondence may be directed to [email protected].
FISP — File Interchange System Protocol