manawenuz/featherChat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
33 Commits 3 Branches 0 Tags
f3e78c6cff9ebf606f5489df75e0725e90a6323e
Commit Graph

3 Commits

Author SHA1 Message Date
Siavash Sameni
f3e78c6cff Group chat with E2E encryption for both web and CLI clients 
Server:
- POST /v1/groups/create — create named group
- POST /v1/groups/:name/join — join group
- GET /v1/groups/:name — get group info + member list
- GET /v1/groups — list all groups
- POST /v1/groups/:name/send — fan-out encrypted messages to members
- Groups stored in sled, members tracked by fingerprint

Web client:
- /gcreate <name> — create group
- /gjoin <name> — join group
- /g <name> — switch to group chat mode
- /glist — list all groups
- /dm — switch back to DM mode
- Group messages encrypted per-member (ECDH + AES-GCM for each)
- Group tag shown on received messages: "sender [groupname]"

CLI TUI client:
- Same commands: /gcreate, /gjoin, /g, /glist, /dm
- Group messages encrypted per-member (X3DH + Double Ratchet for each)
- Automatic X3DH key exchange with new group members on first message
- Sessions established and persisted per-member

Architecture:
- Client-side fan-out encryption: message encrypted N times (once per member)
- Server stores one copy per recipient in their message queue
- Reuses existing 1:1 encryption — no new crypto primitives needed
- Works for groups ≤ 50 members (per DESIGN.md)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-03-26 23:13:16 +04:00
Siavash Sameni
7b1e0bd162 Full web client with E2E encrypted messaging 
Complete single-page web app served at / with:
- Identity generation (random 32-byte seed)
- Identity recovery from hex seed
- Persistent keys in localStorage (survives refresh)
- Auto-load saved identity on page load
- ECDH P-256 key exchange via Web Crypto API
- AES-256-GCM message encryption (iv prepended)
- Key registration with /v1/keys/register
- Send encrypted messages via /v1/messages/send
- Poll for messages every 2s with auto-decrypt
- Peer fingerprint input in header (saved to localStorage)
- Color-coded messages (green=self, orange=peer, cyan=system)
- Lock icon on received encrypted messages
- Commands: /info, /clear, /quit
- Graceful handling of CLI client messages (shows warning)
- Dark theme, responsive, mobile-friendly

Note: web-to-web E2E works. Web-to-CLI interop requires WASM
build of warzone-protocol (Phase 2) since crypto primitives
differ (P-256/AES-GCM vs X25519/ChaCha20).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-03-26 23:05:51 +04:00
Siavash Sameni
7451ad69bc Fix X3DH + add web client served by warzone-server 
X3DH fix:
- Added identity_encryption_key (X25519) to PreKeyBundle
- initiate() and respond() now use correct DH operations per Signal spec:
  DH1=IK_a*SPK_b, DH2=EK_a*IK_b, DH3=EK_a*SPK_b, DH4=EK_a*OPK_b
- All 17 tests pass including x3dh_shared_secret_matches

Web client (served at /):
- Identity generation with seed (stored in localStorage)
- Recovery from hex-encoded seed
- Auto-load saved identity on page load
- Fingerprint display (same format as CLI: xxxx:xxxx:xxxx:xxxx)
- Key registration with server via /v1/keys/register
- Chat UI with message polling (5s interval)
- Commands: /help, /info, /seed
- Dark theme matching warzone aesthetic

Both clients (CLI + Web) now exist:
- CLI: warzone init, warzone info, warzone recover
- Web: http://localhost:7700/ (served by warzone-server)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-03-26 21:32:46 +04:00