History

leetcrypt 1dfc614cc5 feat(hh): P5 — file & directory uploads ⛧ Wire-compatible with the Python client's _ft protocol (offer/accept/reject/ chunk/done, 64KB chunks, SHA-256 verified), over the encrypted channel: - ft.rs: read_payload (file or tar'd directory), save/extract with a zip-slip guard (relative-only, no .. / absolute; unpack_in double-checks), SHA-256. - /send <file> and /sendd <dir>; receiver sees an offer banner, /accept or /reject; chunks stream in the background and the result is verified + saved to ./downloads (directories extracted in place). - Refactor: all outgoing ws frames now funnel through an mpsc channel drained (batched) by the run loop, so the background chunk-sender and the PTY relay transmit without owning the socket. - ui.rs: pending-offer banner on the input bar. Tests: 7 cargo tests (file + dir tar round-trip, traversal guard, + crypto/sbx). Verified live: two TUIs, file and directory transfer, SHA-256 verified, saved. Note: dropping accepted files into the active sandbox VM dir is a future add-on. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-05-30 19:39:55 -07:00
..
downloads	feat(hh): P5 — file & directory uploads ⛧	2026-05-30 19:39:55 -07:00
src	feat(hh): P5 — file & directory uploads ⛧	2026-05-30 19:39:55 -07:00
themes	feat(hh): ratatui TUI client — chat, live roster, themes	2026-05-30 13:57:07 -07:00
tools	chore: rename project coven → hack-house ⛧	2026-05-30 13:29:14 -07:00
Cargo.lock	feat(hh): P5 — file & directory uploads ⛧	2026-05-30 19:39:55 -07:00
Cargo.toml	feat(hh): P5 — file & directory uploads ⛧	2026-05-30 19:39:55 -07:00
README.md	chore: rename project coven → hack-house ⛧	2026-05-30 13:29:14 -07:00
smoke.sh	test: use-case coverage + end-to-end smoke test	2026-05-30 14:15:04 -07:00

README.md

⛧ hack-house ⛧

encrypted collaborative sessions with a summoned sandbox

zero-knowledge server · end-to-end fernet · srp · ratatui

they want you dependent. we want you free.

hack-house is the evolution of cmd-chat: a multi-user, end-to-end-encrypted terminal session where a small crew shares chat, files, and — when summoned — a disposable sandboxed Linux box they drive together, with real Linux permissions and an owner who can delegate the keys.

The server never sees plaintext. Everything — messages, files, terminal output — is relayed as opaque ciphertext. Close the window, the house empties.

status

This is the Rust client (ratatui) for the unchanged Python (Sanic) server. The wire protocol is JSON-over-WebSocket; SRP + HKDF→Fernet are byte-for-byte compatible with the Python srp / cryptography stack.

phase	feature	state
P0	Rust↔Python SRP / Fernet crypto parity	✅ proven (golden vectors + live + cross-lang E2E)
P2	multi-user session (cap 4, infra for more) + authoritative roster	✅ server-side done
P1	ratatui UI (chat, roster, themes)	🚧 in progress
P3	sandbox box (multipass/docker) + shared PTY	⏳ designed (see `../docs/spec-collaborative-sandbox.md`)
P4	permissions (app RBAC + VM unix users / sudo)	⏳ designed
P5	file + directory uploads into the shared session	⏳ designed

crypto parity — the load-bearing proof

$ hack-house selftest            # offline: Rust SRP ≡ Python srp golden vectors
$ hack-house handshake <ip> <port> <name> --password <pw> --no-tls
  ⛧ /srp/verify ok — server identity proven (H_AMK ✓)
  ⛧ round-trip ✓ decrypted: "the house is open ⛧"

tools/gen_vectors.py regenerates the golden vectors from the live Python library (must match the server's _ctsrp backend with rfc5054_enable()).

note: the SRP identity is always the fixed room identity b"chat"; the display name is carried only in JSON, never in the SRP proof. The Python srp package's rfc5054_enable() toggles the active backend's flag — vectors must be generated with the same backend the server actually loads (_ctsrp).

license

MIT · malware bless · hack the planet