Restructure ChaosCrypt from a single-file script into a complete, installable Python package with three interfaces: a typed Python API, an argument-driven CLI, and a bilingual interactive TUI. The algorithm itself is unchanged. Ciphertexts and key files remain fully interoperable with the original implementation in both directions, which is enforced by dedicated tests rather than merely documented. Added - Library API: ChaosCrypt facade plus ChaosCryptCore for the raw algorithm - Unified error hierarchy: 16 named types, all ChaosCryptError subclasses, rendering as ChaosCrypt_ERR_<Detail>_<Code> - CLI: keygen, encrypt, decrypt, file, info, chpwd, tui, with --json output, stdin/stdout piping, and three password sources per secret - Bilingual TUI: English default, runtime switch to Chinese, getpass password entry with a non-TTY fallback that keeps it scriptable - Binary and file support: encrypt_bytes/decrypt_bytes and encrypt_file/decrypt_file - Key management: change_key_password rewraps without altering key material; export_key_text/load_from_text move a key without touching disk - Documentation: SECURITY.md with the full design and threat analysis, plus docs/ covering the API, CLI, architecture and build process - Test suite: 92 tests across round-trips, binary safety, key management, error types, CLI, TUI, i18n and legacy interoperability - Packaging: pyproject.toml, setup.py compatibility shim, MANIFEST.in, py.typed, examples, MIT licence Fixed - Conflicting --pwd option between the -p and -P groups prevented the CLI from starting at all - Wrong key file password reported as file corruption (E002); structural validation now distinguishes it from a damaged file (E003) - export_key_text produced key material without loading it into the instance - Non-hexadecimal input was accepted as ciphertext and silently decrypted into garbage, making corruption indistinguishable from success; malformed input now raises E010 before any processing - TUI failed under piped input because getpass requires a TTY - TUI kept reading the default key file name after generating a new one Changed - Source tree reorganised: the package lives at chaoscrypt/, with tests, examples and legacy alongside it; documentation and build artefacts at the repository root - Code comments unified in English; public docstrings document parameters, return values and raised exceptions - English is now the default UI language - ChaosCryptChat removed from the repository - Attribution updated to Dvs (DvsXT); project URLs point to Gitea
25 lines
750 B
Python
25 lines
750 B
Python
#!/usr/bin/env python3
|
|
"""
|
|
Compatibility shim for legacy build tooling.
|
|
|
|
ChaosCrypt is configured entirely through ``pyproject.toml``. This file exists
|
|
only so that older tools which expect a ``setup.py`` — pip versions predating
|
|
PEP 517 support, ``python setup.py`` invocations, and some packaging scripts —
|
|
still function.
|
|
|
|
All metadata lives in ``pyproject.toml``; nothing is declared here. The call to
|
|
``setup()`` with no arguments lets setuptools read the authoritative
|
|
configuration from the project file, so there is exactly one source of truth.
|
|
|
|
Building is normally done with::
|
|
|
|
python -m build
|
|
|
|
which produces a source distribution and a wheel in ``dist/``.
|
|
"""
|
|
|
|
from setuptools import setup
|
|
|
|
if __name__ == "__main__":
|
|
setup()
|