Metadata-Version: 2.4
Name: cryptnode
Version: 0.2.0
Summary: Managed multi-portal CryptNode client
Requires-Python: >=3.8
Requires-Dist: cryptography==43.0.3
Requires-Dist: tomli==2.2.1; python_version < '3.11'
Description-Content-Type: text/markdown
License-File: BUILD-MATRIX.toml
License-File: FRP-LICENSE
License-File: OPENSSL-LICENSE
License-File: STUNNEL-GPL-2.0.md
License-File: STUNNEL-LICENSE
License-File: STUNNEL-PATCH
License-File: THIRD-PARTY.md

# CryptNode 0.2.0

Install or upgrade with the existing deployment Python environment:
python -m pip install --upgrade cryptnode==0.2.0
python -m pip check
python -c "import cryptnode.host"
crnode --version

If 0.2.0 is already installed, explicitly reinstall the version during maintenance:
python -m pip install --force-reinstall cryptnode==0.2.0

Windows x64 requires machine-level Python 3.8 or newer. Use an administrator terminal and python -s -m pip install --no-user; SYSTEM tasks require the same interpreter and complete machine-accessible dependencies.
Linux x86-64 requires glibc 2.31 or newer, Python 3.8 or newer and systemd; use the existing virtual environment.

Stop running portal instances before updating and resume their previous state after checking the environment. Keep runtime directories, profiles, keys and task definitions. For a new deployment, use crnode deploy followed by crnode load. Check crnode status and crnode doctor.

Dependencies are cryptography==43.0.3 and tomli==2.2.1 below Python 3.11. pip selects the matching platform wheel. Each wheel includes private FRP/stunnel executables and small license/copyright/patch/build-identity files. No credentials are included.

Build 7 preserves the accepted 0.2.0 runtime. Package checks do not prove Windows SYSTEM deployment or production-node acceptance.
