EazyConnect is a Rust platform for LAN file synchronization, encrypted peer messaging, and hardware bridging. It uses CubeHash cellular cryptography, XChaCha20-Poly1305, Ed25519 + X25519, TLS 1.3, and Windows DPAPI / TPM 2.0 / MachineGuid hardware custody.
Legacy Python prototype source (
v0.1.0) remains preserved in thev0.1.0git tag.
- Architecture Overview — 5-crate Rust workspace, CubeHash session lifecycle, signed UDP discovery, and REST / WebSocket routes.
- Security Architecture & Threat Model — Hardware key custody, TOFU Ed25519 pinning, Argon2id/SHA-256 auth, E2E vault format, and blind relay guarantees.
- CLI Reference — Complete options and subcommands for
eazyconnect-serverandeazyconnect-client. - Hardware & Peripheral Bridge — Windows DPAPI, TPM 2.0 CNG probe,
MachineGuidlock, COM/Serial, USB, HID, and encrypted remote hardware bridging. - VPN & Dual-Homed Networks — Mesh VPN setup (WireGuard, Tailscale, ZeroTier), Exit VPN LAN discovery bypass, persistent TLS pinning, and WSS auto-reconnect.
- Changelog — Release history and upgrade notes.
| Crate | Purpose |
|---|---|
crates/cubehash-core |
CubeHash 1.0.2, the vendored cellular 3-cube cryptography engine |
crates/eazyconnect-hw |
Windows DPAPI (CryptProtectData / CryptUnprotectData), TPM 2.0 CNG probe, Registry MachineGuid binding, Win32 adapter/VPN inspection, COM/Serial (serialport), USB (nusb), and Windows HID (SetupAPI/HidD_*) |
crates/eazyconnect-core |
Wire protocol (RelayFrame, 256-byte bucket-padded EazyAppMessage including chunked FileChunk transfers & FileTransferAssembler), Ed25519-signed UDP 37020 LAN discovery beacons, TLS 1.3 CA / SHA-256 pinning, EZV1 E2E file vault envelopes, and BLAKE3 delta manifest |
crates/eazyconnect-server |
Headless HTTPS + WSS Master Server, Argon2id user auth, Ed25519 TOFU device enrollment + invite gate, BLAKE3 file storage host, zero-knowledge blind /ws relay, UDP discovery responder, and Windows startup task helper |
crates/eazyconnect-client |
Headless CLI client, E2E file vault & incremental folder sync, CubeHash E2E terminal chat & chunked P2P file sender (send_e2e_file_bytes), COM/USB/HID inspection & encrypted serial bridging, diagnostics, and Windows logon task helper |
crates/eazyconnect-ui |
Native responsive Discord-style Rust desktop chat UI (eframe/egui) with P2P CubeHash E2E file attachments (+), inline image previews & progress bar, automatic server discovery, TLS pinning & DPAPI enrollment, automatic E2E peer pairing, user profile popout, and Account / Theme / Connection settings |
installer/ |
Simplified 3-card WPF prerequisite & deployment wizard (EazyConnect-Setup.ps1, Setup-EazyConnect.bat) + Inno Setup 6 packager (eazyconnect.iss) |
Requires Rust toolchain (cargo / rustc, Rust 2021 edition).
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
cargo build --release --binsCompiled release binaries are written to:
target/release/eazyconnect-server.exetarget/release/eazyconnect-client.exetarget/release/eazyconnect-ui.exe
You can also run Setup-EazyConnect.bat on Windows to open the graphical prerequisite installer & setup wizard (auto-installing Visual C++ Runtime, Rust toolchain, Git, Inno Setup, firewall rules, shortcuts, and VPN setup hints).
eazyconnect-server --listen 0.0.0.0:8000 --invite-code TEAM-LAN-KEYOn first launch without --admin-pass, eazyconnect-server generates a random CSPRNG password in <data-dir>/bootstrap-admin.txt and prints its TLS SHA-256 Pin and Master Ed25519 public key.
eazyconnect-client discover
eazyconnect-client --master https://<master-host>:8000 --tls-pin <sha256-hex> enroll --invite-code TEAM-LAN-KEYThe enrolled private identity is stored DPAPI-sealed (*.eazyconnect-id.json) and the bearer session token is stored DPAPI-sealed inside config.json.
eazyconnect-client login admin <bootstrap-password>
eazyconnect-client create-user operator "StrongPass#2026"eazyconnect-client sync .\shared-docs --e2e
eazyconnect-client list
eazyconnect-client download report.pdf .\out\report.pdf --e2eWith --e2e, files are encrypted client-side using hardware-bound HKDF + XChaCha20-Poly1305 (EZV1) before upload; the server stores opaque ciphertext only.
CubeHash 1.0.2 changes the peer packet and ratchet format. Upgrade the master first, then update both peers before pairing them again for E2E chat, file transfer, or hardware bridging. The upgraded master can still relay between two older clients.
# Terminal E2E peer chat
eazyconnect-client chat --peer bob --psk shared-secret
# Local hardware inventory & COM serial I/O
eazyconnect-client hw list
eazyconnect-client hw serial list
eazyconnect-client hw serial send COM3 115200 "AT+INFO?"
# Expose local serial hardware over encrypted CubeHash WSS relay
eazyconnect-client hw serial bridge --port COM3 --baud 115200 --psk hw-secreteazyconnect-client profile set --name "Operator" --lang fa
eazyconnect-client diag --uploadRun cargo run -p eazyconnect-ui or open EazyConnect Control Center. Enter the master address, open Network, and sign in with a master administrator account. For a self-signed certificate, enter the TLS SHA-256 pin printed by the master in the sign-in form.
The console refreshes every five seconds while open. It shows relay peers, device enrollment and access status, master uptime, and recent relay activity. Block disconnects an enrolled device and revokes its device token. After an administrator selects Unblock, the device can reconnect with its original identity. The desktop client renews its device token on reconnect if needed. CLI clients can run eazyconnect-client enroll to renew theirs.
Runtime secrets and state (users.json, devices.json, tokens.json, config.json, sync-manifest.json, bootstrap-admin.txt, *.key, *.pem, *.sealed, *.keystore, *keystore*.json, *.eazyconnect-id.json, keystore/, data/, target/) are excluded by .gitignore. Never commit generated runtime directories or keys to a public repository.