merge: fold benchmark + pseudonymous-attribution into main
CI / rust client (hh) (macos-latest) (push) Has been cancelled
CI / rust client (hh) (ubuntu-latest) (push) Has been cancelled
CI / rust coverage (push) Has been cancelled
CI / python server (3.10) (push) Has been cancelled
CI / python server (3.11) (push) Has been cancelled
CI / python server (3.12) (push) Has been cancelled
CI / headless e2e smoke (push) Has been cancelled
CI / dependency audit (push) Has been cancelled
CI / secret scanning (push) Has been cancelled

Integrate the laptop feature branch (multi-language capability benchmark,
model picker, and ESA-style pseudonymous file attribution) onto the current
church main (native AI harness, podman/vbox sandboxes, † theme). Only conflict
was the help/status line — kept the newer podman grammar + /help, spliced in
/export-signed, and aligned attribution strings to the † sigil.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
leetcrypt
2026-07-11 11:22:58 -07:00
20 changed files with 2119 additions and 7 deletions
+38
View File
@@ -0,0 +1,38 @@
# Pseudonymous attribution
hack-house lets you share files **pseudonymously but provably** — a recipient can
verify *who* authored a file (and that it's intact) without anyone, including the
relay server, learning your real identity. It adapts Princess_Pi's
**Encrypt-Share-Attribution** scheme from the Church of Malware codex
(<https://git.thecoven.info/PrincessPi/Encrypt-Share-Attribution>).
There are two independent ways to prove authorship, mirroring ESA:
1. **Persona signature (automatic).** On first run each client mints a long-lived
Ed25519 "persona" key at `~/.config/hack-house/persona_ed25519` (0600). Every
`/send` / `/sendroom` offer carries the persona public key and a detached
signature over `attest-v1 || sha256 || name || size`. Receivers verify it and
see the persona **fingerprint** (`⛧<8 hex>`), so the same author is recognizable
across offers. The fields are additive JSON — a Python peer that doesn't sign
still interoperates (its offers just show as *unsigned*).
2. **Attribution passphrase (opt-in).** Add `--attest <passphrase>` to a send:
the offer then carries a commitment `SHA-512(passphrase || sha256)`. You can
*later* reveal the passphrase to prove authorship to anyone, even people who
weren't in the room.
## Commands
```
/send <user> <path> [--attest <passphrase>]
/sendroom <path> [--attest <passphrase>]
/export-signed <dir> [--attest <passphrase>]
```
`/export-signed` packages a directory into a **portable, self-verifying ESA 7z
archive** (`verifiable_archive_<ts>.7z`) using Princess_Pi's exact format: a fresh
per-round Ed25519 key signs an inner `contents.7z`, SHA-512 checksums cover the
outer layer, and bundled `verify-everything.sh` / `test_validate_passphrase.sh`
let anyone with `bash` + `7z` + `ssh-keygen` verify it — no hack-house needed. The
builder is `hh/tools/esa/esa_build.sh` (embedded in the binary). Requires `7z`,
`ssh-keygen`, `sha512sum`, `shred`, `openssl` on the host.