Problem: Windows CLI client window closing immediately on error without error messages
Changes:
1. Wrapped main in error handler with pause before exit
2. Replaced .unwrap() with proper .context() error handling
3. Added pause on all error paths
4. Error display with colored output before exit
5. Updated ostp-client.exe checksum
Now on error:
- Error message displayed in red
- Press Enter to exit keeps window open
- User can read full error details
Note: NO GUI - ostp-client.exe is CLI tool
Usage:
- ostp-client.exe connect --server IP:PORT --psk KEY --country US
- ostp-client.exe setup (interactive wizard)
SHA256: 5612ae4503467d6d7b51c067f533706bc65b7b7ac41fccc3efaf3eda2576b92a
Problem:
Client terminal was closing immediately on connect command because
todo!() macros in TUN interface and relay functions were causing panics.
Changes:
1. ✅ Replaced create_tun_interface() todo with stub returning dummy interface
2. ✅ Replaced configure_routing() todo with stub (no-op)
3. ✅ Replaced cleanup_routing() todo with stub (no-op)
4. ✅ Replaced relay_traffic() todo with infinite sleep (keeps connection alive)
5. ✅ Added warning messages with yellow ⚠ indicator for stub functions
6. ✅ Updated SHA256SUMS for both packages
7. ✅ Recreated distribution archives
8. ✅ Added CONFIG_FILES.md explaining server-enrollment.json.example usage
Client Behavior Now:
- Connection establishes successfully
- Shows [STUB] warnings for TUN/routing/relay
- Stays connected (Ctrl+C to exit)
- No actual traffic forwarding yet (TODO for next iteration)
server-enrollment.json.example Usage:
- For Standalone mode (connecting to existing Master Node)
- Requires enrollment_token from admin
- psk: 'AUTO' until approved
- See CONFIG_FILES.md for detailed workflow
Next Steps:
- Implement real TUN interface using osn crate
- Implement route configuration via ip command
- Implement packet relay loop (TUN ↔ OSTP client)
- Add daemon mode (fork + detach)
Distribution:
- ostp-server-linux-x64.tar.gz: 6.85 MB
- ostp-client-linux-x64.tar.gz: 0.92 MB (updated client)
- Build static musl binaries (work on any Linux distro)
- Redesign ostp-guard with weighted scoring system (threshold: 4 points)
- HIGH (2pts): Analysis tools (gdb/ida/ghidra), sandbox artifacts
- MEDIUM (1pt): Low resources (<1GB RAM), suspicious env vars
- Production VPS safe (1-2 points), sandbox blocked (4+ points)
- Anti-debug: Windows (IsDebuggerPresent), Linux (/proc/self/status)
- Deployment packages for Linux + Windows with SHA256 checksums
