2 Commits
Author SHA1 Message Date
dvs a2d492e9f8 Add dvs_enc.py and document the two-module requirement
The client imports its backend from a module named `dvs_enc`, but the
repository only shipped that backend as `qtmain.py`. Starting the application
from a fresh clone therefore failed immediately:

    ModuleNotFoundError: No module named 'dvs_enc'

`dvs_enc.py` is now included. It carries the same content as `qtmain.py`, so
the import resolves to the identical implementation.

Verified end to end:

  - without dvs_enc.py: import qtmain raises ModuleNotFoundError
  - with dvs_enc.py:    import qtmain succeeds, all 14 backend classes present

Functional tests against a clean copy of the repository pass: text
round-trip, 4096-byte binary round-trip, HMAC authentication, AccountDB and
HistoryDB construction.

Also exercised the full client/server protocol against a live relay: register,
login, create group, join group, and ciphertext relay between two clients.
The relay forwards the payload verbatim without inspecting it.

Documentation
- README: new "Module layout" section explaining why both files are required,
  and what the failure looks like when dvs_enc.py is absent; repository layout
  and troubleshooting table updated to match
- CHANGELOG: structure table updated
v3.0.0
2026-09-27 17:16:56 +08:00
dvs faf60fd2e5 v3.0.0: Standalone release of ChaosCryptChat
Separate the encrypted messaging application into its own repository, with
documentation written specifically for it.

The application code is byte-for-byte identical to the version previously
shipped inside the ChaosCrypt repository. No functional changes.

Contents
- qtmain.py: PyQt5 client together with the complete backend (cipher core,
  account and history databases, peer-to-peer networking, relay client, GUI)
- server.py: optional central relay server, using only the standard library
  so it can be deployed on a bare machine

Documentation
- README: architecture, component map, wire protocol, requirements,
  installation, running, data locations, security properties, troubleshooting
- SECURITY: threat model, protected properties, cryptographic building
  blocks, and known limitations including metadata exposure, plaintext local
  storage, P2P host trust, best-effort withdrawal, and the absence of a
  ratchet
- LICENSE: MIT
- CHANGELOG: release history
- .gitignore: excludes application data, session tokens, local databases and
  media from version control

Security notice
Unaudited. Intended for learning, experimentation and personal use; not for
production deployment or for confidentiality obligations that carry a
regulatory, contractual or safety dimension.
2026-09-27 17:11:06 +08:00