Terminal Server Edition
A minimal, terminal-only live ISO based on Debian 13 (Trixie) crafted for two critical missions: bulletproof testing of the full Kodachi toolchain and operating as a dedicated SOCKS proxy gateway for your network.
Download & Installation First Release: 30 October 2025 9.8.4 Queen | Terminal last updated 26 June 2026 - build #183
Download ISO
Direct download
LatestDownload the latest Kodachi Terminal Server ISO directly. One-click access to the current release (linux-kodachi-terminal-9.0.1-amd64.iso, approximately 2.4GB).
Verify the downloaded ISO file integrity using the SHA256 checksum below to ensure secure installation:
c1140c7d9f75288b4aeb1f1cb6b961a291172f0deee2cbb8f6f71c5b9ebf0678
Verification command
sha256sum linux-kodachi-terminal-9.0.1-amd64.iso
GPG signature verification available
GPG signature files for cryptographic verification are available on the Kodachi download page. Download the signature files from the same location:
linux-kodachi-terminal-9.0.1-amd64.iso.sig(GPG signature file)linux-kodachi-terminal-9.0.1-amd64.iso.sig.info(signature information)
Prefer browser-based verification? Use the File Verification tool to compute hashes and compare against all official Kodachi checksums automatically.
Kodachi is built and maintained by one person since 2013
If this ISO is useful to you or your organisation, please consider supporting the project before you leave.
Installation Methods
Bare metal
Install on dedicated hardware for maximum performance as a proxy server.
Virtual machine
Run in VMware, VirtualBox, or QEMU for an isolated testing environment.
Live USB
Boot from USB drive: no installation, portable, leaves no traces.
Persistent storage
Enable persistence for configuration retention across reboots.
Login credentials
kodachiSecurity4AllThese are the live/default kodachi account credentials. root login is disabled and does not use this password.
Create Bootable USB
| Tool | Platform | Multiboot | Best for |
|---|---|---|---|
| Ventoy | Linux, Windows | Yes | Drag-and-drop multiple ISOs |
| Rufus | Windows | No | Industry standard, DD or ISO mode |
| Etcher | Linux, Windows, macOS | No | Simplest three-step flash |
| YUMI | Windows | Yes | Add multiple OSes one at a time |
| UUI | Windows | No | Single-OS from the YUMI team |
Linux dd (recommended)
# Find USB device
lsblk
# Write ISO to USB (replace /dev/sdX with your USB device)
sudo dd if=linux-kodachi-terminal-9.0.1-amd64.iso of=/dev/sdX bs=4M status=progress oflag=sync
macOS dd
# Find disk identifier
diskutil list
# Unmount disk
diskutil unmountDisk /dev/diskN
# Write ISO
sudo dd if=linux-kodachi-terminal-9.0.1-amd64.iso of=/dev/rdiskN bs=4m
WARNING: dd will overwrite all data on the target drive
Double-check the device identifier before running the dd command. Using the wrong device will permanently erase that drive's contents.
Technical Specifications Dashboard
| Component | Details |
|---|---|
| Base System | Debian 13 (Trixie) |
| Architecture | amd64 (x86_64) |
| ISO Size | Approximately 2.4GB (lightweight, no GUI bloat) |
| Total Packages | 1,603 packages (from linux-kodachi-terminal-9.0.1-amd64.packages) |
| Terminal Packages | 250 terminal-specific packages (uncommented entries in terminal.list.chroot) |
| Base Common | 46 shared base packages (from live.list.chroot) |
| Firmware Packages | 23 firmware and microcode packages (WiFi, Ethernet, Bluetooth, GPU, CPU) |
| Kodachi Binaries | 28 binaries pre-installed in /opt/kodachi/dashboard/hooks/ (18 Kodachi core services and dashboard, 2 companion tools, 8 KAICS AI) |
| Desktop Conky Telemetry | conky-status (Conky details, legacy conky-details naming) ships in the unified binary pack, but its Conky desktop display is only used on Desktop XFCE builds (the terminal edition has no GUI) |
| Interface | Terminal-only (no GUI) |
| Boot Support | BIOS + UEFI compatible |
| Login Credentials | Username: kodachi / Password: Security4All |
| Sudo Access | Passwordless sudo enabled |
Package Categories Breakdown
| Category | Count | Signature packages |
|---|---|---|
| Hardware Firmware & Drivers | 23 | firmware-iwlwifi, firmware-realtek, firmware-atheros, broadcom-sta-dkms |
| Networking Tools & Utilities | 26 | nmap, tcpdump, tshark, whatweb, netcat-openbsd, macchanger, mtr |
| VPN & Anonymity Infrastructure | 7 | tor, openvpn, wireguard-tools, shadowsocks-libev, torsocks, obfs4proxy, openconnect |
| Proxy & Traffic Control | 8 | iptables, nftables, proxychains, redsocks, socat, haproxy, microsocks |
| Security & Privacy Tools | 19 | gnupg2, ufw, firejail, apparmor, steghide, mat2, bind9-dnsutils |
| Security Auditing & Monitoring | 8 | aide, auditd, usbguard, bpftrace, sysstat, ltrace |
| Build & Crypto Headers | runtime-only | Runtime crypto libs and Python tooling (e.g. libssl3, python3-pip, shellcheck). The matching -dev headers (libssl-dev, linux-headers-amd64, etc.) are excluded: they are compile-time only and not needed at runtime. |
| Compression & Archive Tools | 10 | p7zip-full, zstd, unp, unace, cabextract, arj |
| System Monitoring & Diagnostics | 18 | btop, fastfetch, inxi, nethogs, vnstat, iperf3, smartmontools, lm-sensors |
| Filesystem & Disk Management | 28 | cryptsetup, btrfs-progs, xfsprogs, ntfs-3g, testdisk, gddrescue, clonezilla, nvme-cli |
| CLI Utilities & Enhancements | 62 | neovim, xxd, ripgrep, fd-find, fzf, bat, lazygit, yq, w3m, tree, lsof |
| Hardware Support (Bluetooth & Scanner) | 8 | bluez, bluetooth, rfkill, sane-utils, sane-airscan |
| Fonts & Localization | 1 | wamerican |
| Virtualization & System Integration | 3 | open-vm-tools, samba-libs, apt-transport-https |
| Power & Firmware Management | 3 | tlp, tlp-rdw, fwupd |
| Additional Applications & Crypto Wallets | 4 | onionshare-cli, wireless-regdb, electrum, monero |
| Base Debian Live (common) | 46 | live-boot, network-manager, openssh-server, git, build-essential, tmux, htop |
| AI & Intelligence | 8 | KAICS tools (ai-cmd, ai-gateway, and 6 related binaries) are pre-installed as part of the 28-binary pack |
| Base System (total ISO) | 1,603 | Debian core utilities, libraries, and runtime dependencies from the ISO manifest |
Pre-Installed Kodachi Binaries
All 28 terminal binaries are pre-installed at /opt/kodachi/dashboard/hooks/: 18 Kodachi core services and the dashboard binary, 2 companion tools (oniux and tun2socks-linux-amd64), and the 8 KAICS ai-* binaries. Launch the toolkit instantly without additional setup.
Headless caveat: kodachi-dashboard is the GUI Tauri binary and ships in the shared unified pack, but it is inert on the terminal edition (no display server to render it). The Rust conky-status telemetry gateway (Conky details binary, legacy conky-details naming) is likewise present, but its Conky desktop display is only active on Desktop XFCE builds.
Dependency installer additions: the package list above covers entries declared in terminal.list.chroot / live.list.chroot. The build also runs kodachi-deps-install.sh from its chroot hook (9999-zzz-kodachi-install) to guarantee the privacy and hardening stack is present even when a package is not in those lists. The following reach the ISO through the installer script rather than the package list:
On a standalone (non-live) Debian system you can install the same dependency stack yourself with sudo bash kodachi-deps-install.sh; the matching Kodachi binaries are installed by kodachi-binary-install.sh, and kodachi-debug-collector.sh gathers diagnostics for support without installing anything.
Supported Routing Protocols
Kodachi Terminal Server ships with 11 auto-scored routing protocols (plus xray-vmess as a legacy fallback) via the routing-switch binary, covering everything from battle-tested VPNs to advanced censorship-resistant transports.
| Category | Protocols & features |
|---|---|
| VPN Protocols | OpenVPN (industry-standard, AES encryption), WireGuard (modern, ChaCha20 encryption), with kill switch and DNS leak protection |
| Anti-Censorship | Shadowsocks (SOCKS5 + encryption), V2Ray (traffic obfuscation), Xray (enhanced V2Ray), Hysteria2 (high-performance for restrictive networks), Mieru (MITA, lightweight anti-censorship proxy) |
| Proxy Protocols | SOCKS5 (standard proxy), Dante (SOCKS server), HTTP/HTTPS (proxy support), Microsocks (lightweight SOCKS5 server) |
| Tor Integration | Redsocks (transparent Tor routing), SOCKS proxy configuration, TransPort routing, DNS over Tor, System-wide torrification (can run on top of any existing VPN service: WireGuard, OpenVPN, Hysteria2, Shadowsocks, V2Ray, Xray, Mieru). The remote Tor route is VPN-only: connect WireGuard or OpenVPN first, then it layers Tor on that tunnel. The worker Tor SOCKS port is never exposed on a public IP (an open Tor SOCKS proxy gets abused), so it is reachable only from inside the Kodachi VPN network. |
| Multi-Layer | VPN + Tor (double encryption), protocol chaining for enhanced anonymity, traffic obfuscation layers |
Protocol documentation
For detailed protocol configuration and usage, see the routing-switch documentation.
Torrification capability
Kodachi Terminal supports system-wide torrification that can run on top of any existing VPN service. This means you can layer Tor routing on top of WireGuard, OpenVPN, Hysteria2, Shadowsocks, V2Ray, or Xray connections for enhanced anonymity. Use sudo tor-switch torrify-system-nftables-dns (preferred) or sudo tor-switch torrify-system-iptables-dns to torrify your entire system regardless of your underlying VPN connection. To disable, use sudo tor-switch detorrify-system-nftables or sudo tor-switch detorrify-system-iptables.
Security Models & Layered Anonymity
Kodachi Terminal includes 96 pre-built security workflows and supports unlimited custom workflows via the workflow-manager binary. The 18 example workflows below are organized by anonymity level, from maximum-deniability triple-VPN-plus-Tor chains down to fast single-VPN daily-use profiles. All profiles live in /opt/kodachi/dashboard/hooks/config/profiles/; create, modify, and chain them with workflow-manager.
Full 18-workflow walkthrough on the Desktop page
The complete, per-workflow reference (full chain diagrams, ideal-for notes, and the exact routing-switch / tor-switch commands for each) is documented once as the canonical copy. The workflows are identical across editions (pure CLI, no GUI equivalent).
Workflow Comparison Matrix
| # | Chain summary | Anonymity | Speed |
|---|---|---|---|
| 01 | Router VPN, Host Mullvad, VM WireGuard, Torrified | Ultra++ (6/6) | Slowest |
| 02 | Router VPN, Host ProtonVPN, VM OpenVPN, Torrified | Ultra++ (6/6) | Slowest |
| 03 | Router VPN, Host NordVPN, VM Shadowsocks, Torrified | Ultra++ (6/6) | Very Slow |
| 04 | Host Mullvad, VM OpenVPN, Torrified + Tor DNS | Ultra (5/5) | Slow |
| 05 | Host ProtonVPN, VM Shadowsocks, Torrified + Tor DNS | Ultra (5/5) | Slow |
| 06 | Host NordVPN, VM V2Ray, Torrified + Tor DNS | Ultra (5/5) | Moderate |
| 07 | Host ExpressVPN, VM Hysteria2, Torrified + Tor DNS | Ultra (5/5) | Moderate |
| 08 | Anonymous VPN, Tor, Torrified + Tor DNS | Ultra (5/5) | Slow |
| 09 | Forced Xray, Torrified + Tor DNS | Very High (4.5/5) | Very Slow |
| 10 | WireGuard, Torrified + Tor DNS | Very High (4.5/5) | Slow |
| 11 | Router VPN, VM WireGuard, Tor (single Tor) | Very High (4.5/5) | Slow |
| 12 | Host Mullvad, VM Shadowsocks, DNSCrypt | High (4/5) | Good |
| 13 | Host ProtonVPN, VM Hysteria2, DNSCrypt | High (4/5) | Very Good |
| 14 | Host ExpressVPN, VM Xray-VLESS-Reality, DNSCrypt | High (4/5) | Good |
| 15 | Forced Hysteria2, Torrified + Tor DNS | Moderate-High (3.5/5) | Moderate |
| 16 | V2Ray, Torrified + Tor DNS | Moderate-High (3.5/5) | Moderate |
| 17 | Anonymous Shadowsocks, Tor + Tor DNS | Moderate-High (3.5/5) | Moderate |
| 18 | Forced OpenVPN, DNSCrypt (fast performance) | Moderate (3/5) | Fast |
Protocol-Specific Initial Setup Workflows
Kodachi Terminal Server includes ready-to-use initial setup profiles for multiple routing protocols:
VPN Protocols:
initial_terminal_setup_openvpn_only- OpenVPN connection setupinitial_terminal_setup_wireguard_only- WireGuard connection setup
Anti-Censorship Protocols:
initial_terminal_setup_shadowsocks_only- Shadowsocks proxy setupinitial_terminal_setup_v2ray_only- V2Ray traffic obfuscationinitial_terminal_setup_xray_vless_only- Xray VLESS protocolinitial_terminal_setup_xray_trojan_only- Xray Trojan protocolinitial_terminal_setup_xray_vless_reality_only- Xray VLESS Realityinitial_terminal_setup_hysteria2_only- Hysteria2 high-performance
Proxy Servers:
initial_terminal_setup_dante_only- Dante SOCKS5 serverinitial_terminal_setup_mita_only- Mieru/MITA pluggable proxy (anti-censorship)
Tor Combinations:
initial_terminal_setup_tor_only- Tor-only setupinitial_terminal_setup_wireguard_torrify- WireGuard + Tor torrificationinitial_terminal_setup_auth_torrify_only- Authentication + Tor torrification
Execute with: sudo workflow-manager run <profile-name>
Organized by anonymity tiers. Six tiers step down from maximum-deniability triple-VPN-plus-Tor chains to fast single-VPN daily use. Each tier maps to a range of the 18 example workflows above.
Triple VPN protection with Tor torrification.
Configuration chain
Best for
Double VPN with Tor torrification.
Configuration chain
Best for
Double Tor circuits or Router + Guest VPN + Tor.
Configuration chain
Best for
Double VPN layer.
Configuration chain
Best for
Single VPN with Tor.
Configuration chain
Best for
Single VPN with encrypted DNS.
Configuration chain
Best for
Create Custom Workflows
Use workflow-manager for: Multi-protocol chains, adaptive failover, custom threat models, automated security responses, and specialized use cases.
NOT Recommended: Tor → VPN
Avoid Configuration: Your Computer → Tor → VPN → Internet
This configuration is widely discouraged; it blocks .onion access, lets the guard see your real IP, makes Tor usage detectable, degrades performance, and shifts trust to the VPN.
Why this is dangerous: Entry nodes see your real IP • ISP detects Tor usage • NO access to .onion sites • Severely degraded performance • VPN provider can see your activity
Evidence: For detailed analysis, read the Tor Project's official documentation on Tor+VPN configurations.
Source Information
Based on Privacy Guides 2025 recommendations, Tor Project official documentation, and Kodachi security research. These workflows represent comprehensive threat modeling from maximum anonymity to secure financial operations.
SOCKS Proxy Server Setup (Primary Use Case)
One of Kodachi Terminal's primary use cases is running as a dedicated SOCKS proxy server for your entire network. This allows all devices (phones, tablets, computers) to route traffic through a single anonymized gateway.
Step-by-Step Server Setup
1. Boot Kodachi Terminal Server on dedicated hardware or VM
These are the live/default kodachi account credentials. root login is disabled and does not use this password.
2. Configure network routing
sudo routing-switch connect wireguard # Connect to VPN
sudo tor-switch torrify-system-nftables-dns # Torrify system + Tor DNS
sudo dns-switch switch --names dnscrypt-quad9 # Privacy-focused DNS
3. Start SOCKS proxy server (choose one)
Option A: V2Ray SOCKS5 proxy (recommended for performance)
# Configure V2Ray with SOCKS5 inbound
v2ray run -config /path/to/config.json
# Default SOCKS5 port: 10808
Option B: Microsocks lightweight proxy
Option C: Dante SOCKS server (enterprise-grade)
sudo apt install dante-server
sudo systemctl start danted
# Configure /etc/danted.conf for your network
4. Configure client devices
Point all devices on your network to use:
- SOCKS5 Server:
<Kodachi-Terminal-Server-IP>:30050(or your chosen port) - Protocol: SOCKS5
5. Verify proxy is working
sudo ip-fetch fetch # Check exit IP
health-control net-check # Verify no leaks
sudo dns-leak test # DNS leak test
Managing the Proxy Server
# Monitor active proxy connections
sudo netstat -tulpn | grep microsocks
# Configure firewall to restrict proxy access to trusted IPs
sudo iptables -A INPUT -p tcp --dport 30050 -s TRUSTED_IP -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 30050 -j DROP
Flag meaning: microsocks -p vs routing-switch -p
The raw microsocks -i 0.0.0.0 -p 30050 invocation above uses that upstream tool's own CLI where -p is the listen port. The Kodachi wrapper shown later (routing-switch microsocks-enable -u <user> -p <password> [--port <n>]) uses -p for the password and --port for the port. Both are individually correct for their respective binaries.
Use Case Examples
V2Ray proxy server for network
Boot Kodachi Terminal Server on an old laptop, connect to VPN, start a V2Ray SOCKS5 server, and configure all home devices to use the proxy. The entire household is anonymized.
VMware testing environment
Run in VMware Workstation or Fusion to test all 28 pre-installed terminal binaries safely. Snapshot before testing, roll back after experiments, no impact on the host system.
Dedicated proxy server hardware
Boot on an old desktop or laptop, enable persistent storage, configure routing protocols, and run 24/7 as a network proxy gateway for centralized anonymity across all devices.
Internet cafe / public computer
Boot from USB with no installation required, use the Kodachi binaries for secure browsing, then shut down. No traces are left on the host machine.
Travel & hotels
Boot on a travel laptop, connect to hotel WiFi, enable VPN and Tor, access sensitive accounts securely, and bypass local censorship or monitoring.
Corporate / educational testing
Security researchers can test Kodachi binaries in an isolated VM, learn the CLI commands, and verify routing configurations in a safe environment for experimentation.
Advanced Configuration
Persistent Storage & Encrypted Persistence
Automatic Persistence Setup (Recommended)
Most USB creation tools handle persistence automatically! When creating your bootable USB, select the persistence option in these tools:
- Rufus (Windows) - Select "Persistent partition size" slider when writing the ISO
- UUI (Universal USB Installer) - Check "Persistent file size for storing changes" option
- YUMI (Multiboot) - Supports persistent storage configuration during setup
See the Create Bootable USB section above for tool downloads and setup.
No manual commands needed - The tools will automatically create and configure the persistent partition for you!
Boot Options:
- live-persist - Enable persistent storage (standard)
- live-persist-encrypted - Enable encrypted persistent storage (recommended for security)
health-control Persistence Management:
For advanced users, health-control provides automated persistence creation:
# Create encrypted persistence (recommended)
sudo health-control create-persistence --encrypted
# Custom size (8GB)
sudo health-control create-persistence --encrypted --size 8192
# Safety check device first
sudo health-control list-storage-devices
sudo health-control usb-safety-check --device /dev/sdX
See Also
For complete documentation of persistence management, encrypted containers, storage encryption, and safety features, see the health-control documentation.
Emergency Data Destruction (Nuke Password)
What is Nuke Password?
The nuke password feature allows instant, irreversible destruction of encrypted data in emergency scenarios by destroying LUKS encryption keys, making data permanently unrecoverable.
Requirements
- Encrypted persistent storage (
live-persist-encryptedboot option) - LUKS-encrypted partition
health-controlbinary (Kodachi system binary)cryptsetup-nuke-passwordpackage (pre-installed in the ISO viaterminal.list.chroot)
Recommended Method: Using health-control
The health-control binary provides a safe, automated approach to managing nuke passwords with built-in safety features:
# Step 1: Detect LUKS devices on your system
health-control luks-detect
health-control luks-detect --all-devices # Include loop and virtual devices
health-control luks-detect --json # JSON output for scripts
# Step 2: Configure nuke password (Interactive - Recommended)
sudo health-control luks-nuke --action configure --device /dev/sda5
# Prompts for nuke password interactively (safer method)
# OR: Configure with password (Automated - for scripts)
sudo health-control luks-nuke --action configure --device /dev/sda5 --password YOUR_NUKE_PASSWORD
# Step 3: Verify nuke password is configured
health-control luks-nuke --action status # Check all LUKS devices
health-control luks-nuke --action status --device /dev/sda5 # Check specific device
health-control luks-nuke --action status --json # JSON output
# Optional: Remove nuke password
sudo health-control luks-nuke --action remove --device /dev/sda5
Safety Features
When using health-control for nuke password management, you get:
- Automatic LUKS Validation: Verifies device is actually a LUKS partition before operations
- Encrypted Header Backup: Creates AES-256-CBC encrypted backup of LUKS header on Desktop (timestamped)
- Package Management: Auto-installs
cryptsetup-nuke-passwordif not present - Comprehensive Logging: All operations logged to
logs-hookfor audit trail - Status Monitoring: Check nuke password status across all LUKS devices
- JSON Support: Full JSON output for GUI/dashboard integration
Advanced/Manual Method
For advanced users who prefer direct control, you can use the underlying cryptsetup command:
# Add nuke password to existing LUKS partition (manual method)
sudo cryptsetup luksAddNuke /dev/sdX2
# You'll be prompted to:
# 1. Enter existing LUKS password
# 2. Enter new NUKE password (different from normal password)
# 3. Confirm nuke password
# <i class="fas fa-exclamation-triangle" style="color: #ff9800;"></i> WARNING: Manual method does NOT create header backups
# Consider using health-control for automated safety features
How It Works
- Normal Boot: Enter regular LUKS password → Data decrypted normally
- Emergency Activation: Enter nuke password → LUKS header destroyed instantly → Data permanently unrecoverable
- Result: Partition appears as random data, no forensic recovery possible
Activation Process
# During boot, when prompted for LUKS password:
# Enter NUKE password instead of normal password
# → LUKS header immediately destroyed
# → Boot fails (expected)
# → Data permanently destroyed
Use Cases
- Border crossings / checkpoints under duress
- Emergency situations requiring immediate data destruction
- Physical device seizure scenarios
- Coercive password disclosure situations
Critical Warning
Nuke password destroys ALL data on the encrypted partition permanently. There is NO recovery, NO undo, NO backup restoration. Use only in genuine emergency scenarios. Test in a non-critical environment first.
Backup & Restore
Kodachi ships kodachi-backup, an encrypted backup and restore tool for your personal data, built so you can preserve your files before downloading a new ISO and restore them on the new system afterwards. It wraps restic (encrypted, deduplicated, versioned) and runs entirely from the shell on the Terminal edition.
# Back up to an encrypted volume (LUKS / VeraCrypt / dm-crypt auto-detected)
# Add --allow-unencrypted to target an ordinary drive (you will be prompted to confirm)
kodachi-backup backup --target /media/usb
# Restore the latest snapshot into a safe ~/Restored-<date> staging folder
kodachi-backup restore --target /media/usb
# Restore straight to original locations (overwrites current files)
kodachi-backup restore --target /media/usb --in-place
# Integrity check / list snapshots / show status
kodachi-backup verify --target /media/usb
kodachi-backup list --target /media/usb
kodachi-backup status --target /media/usb
# Manage custom folders and view the full backup list
kodachi-backup categories # list all what-to-back-up entries as JSON
kodachi-backup add-path --path <dir> # add a custom folder to the backup list
kodachi-backup remove-path --path <dir> # remove a custom folder from the backup list
What is and isn't backed up
Backs up your data only, Documents, Downloads, Pictures, Videos, Music, Desktop, Public, Templates, plus ~/.gnupg, ~/.ssh, password stores and the LibreWolf profile. It excludes desktop and system configuration (~/.config, ~/.cache, ~/.kde, ~/.local) so a restore can never break a freshly installed ISO. Customize the lists at ~/.config/kodachi/backup/include.list and exclude.list.
Custom folders and crypto wallets
You can back up any folder by running kodachi-backup add-path --path <dir>. Common crypto wallets are automatically included when they exist on disk: Monero (~/.bitmonero and ~/Monero), Bitcoin Core (~/.bitcoin), Electrum (~/.electrum), and Wasabi (~/.walletwasabi). All entries are persisted in ~/.config/kodachi/backup/include.list. Use kodachi-backup categories to see the full list as JSON. Note: wallet data stored under ~/.config is excluded by the desktop-config exclusion rule; the wallets listed above store outside ~/.config and are backed up correctly.
Encryption detection and unencrypted drives
LUKS, VeraCrypt/TrueCrypt, and other dm-crypt volumes are detected automatically. By default, unrecognised (unencrypted) drives are refused. Pass --allow-unencrypted to opt in, you will be warned and must confirm. Restic still encrypts the backup with your passphrase regardless; only the drive's full-disk-encryption layer is absent.
Passphrase
The repository passphrase is never stored, you are prompted on the command line, or you can set the RESTIC_PASSWORD environment variable. You need the same passphrase to restore. Add --json for machine-readable output.
Hardware Support Matrix
Kodachi Terminal Server bundles 30+ firmware packages to deliver broad WiFi, Ethernet, Bluetooth, GPU, and microcode coverage out of the box.
WiFi
Ethernet
Plus standard kernel-supported chipsets (Intel e1000/igb/ixgbe, Atheros). Enterprise NIC firmware (bnx2/x, Cavium, Myricom, Netronome, QLogic) intentionally excluded per 24 April 2026 hardware audit (not present on desktop/laptop/VM targets).
Bluetooth
GPU / Graphics
Microcode
Broadcom Wireless Support - Pre-Installed
No post-boot installation requiredBroadcom b43 and b43legacy firmware is pre-installed in the ISO at /lib/firmware/b43/ and /lib/firmware/b43legacy/. Firmware is ready to use immediately.
Supported chipsets
Drivers included
- b43 kernel driver (open-source, loaded automatically)
- b43legacy kernel driver (for BCM4301-4306/2)
- broadcom-sta-dkms wl proprietary driver, alternative for some cards
- b43-fwcutter tool (if you need to extract different firmware versions)
Troubleshooting
Issue: WiFi not working
# Check WiFi hardware
lspci | grep -i wireless
# Install missing firmware (if needed)
sudo apt update
sudo apt install firmware-iwlwifi firmware-realtek
sudo modprobe -r iwlwifi && sudo modprobe iwlwifi # Reload driver
Issue: Shift+2 prints " instead of @ in virtual machines
QEMU CLI: add the US keymap flag when launching.
qemu-system-x86_64 \
-m 4096 \
-enable-kvm \
-k en-us \
-cdrom kodachi-live.iso \
-boot d
virt-manager: open the VM settings, then Overview, then Display Spice or Display VNC, and set Keyboard Layout to English (US).
VirtualBox: Settings, General, Advanced, choose English (US) for keyboard layout, or run VBoxManage modifyvm "Kodachi VM" --keyboard-layout "English (US)".
Issue: Binary not found
# Verify binaries exist
ls -la /opt/kodachi/dashboard/hooks/
# Check PATH
echo $PATH
# Run with sudo
sudo ip-fetch
Issue: VPN not connecting
# Check VPN configuration
sudo routing-switch status
# Verify network connectivity
ping -c 4 1.1.1.1
# Check DNS resolution
nslookup check.torproject.org
# Review logs
tail -f /opt/kodachi/dashboard/hooks/logs/routing-switch.log
Issue: Tor not starting
# Check Tor service status
sudo systemctl status tor
# Review Tor logs
sudo journalctl -u tor -f
# Restart Tor service
sudo tor-switch stop-tor
sudo tor-switch torrify-system-nftables-dns
Issue: DNS leaks detected
# Switch DNS provider
sudo dns-switch switch --names dnscrypt-quad9
# Test again
sudo dns-leak test --comprehensive
# Verify DNS configuration
cat /etc/resolv.conf
Security Considerations
Recommended Security Measures
Always verify downloaded ISOs
Check SHA256 checksums before you boot.
Use encrypted persistent storage
Enable the live-persist-encrypted boot option.
Configure a nuke password
For emergency data destruction under duress.
Restrict proxy access
Use firewall rules to limit which client IPs can reach the proxy.
Regular updates
Keep system packages updated (if using persistence).
Monitor logs
Review service logs for anomalies.
Test workflows
Verify anonymity configurations before production use.
Backup configurations
Export VPN and proxy configurations separately.
Physical security
Secure the hardware running the proxy server.
Network segmentation
Isolate the proxy server on a dedicated network.
Related Documentation
- Installation Guide - General installation instructions for Kodachi binaries
- Binaries Overview - Complete reference for Kodachi binaries
- routing-switch Documentation - Detailed routing-switch commands
- tor-switch Documentation - Tor network management
- health-control Documentation - System health and emergency controls
- AI & Intelligence Tools - KAICS: Natural language commands, monitoring, and AI automation
Summary
Kodachi Terminal Server is the ideal solution for:
Key benefits
Network-wide proxy protection: run as a dedicated SOCKS5 server.
Safe binary testing: an isolated environment for experimentation.
Multi-protocol support: 11 routing protocols included.
Resource efficient: lightweight terminal-only design (approximately 2.4GB ISO).
Production ready: based on Debian 13 (Trixie) with comprehensive hardware support.
Complete toolkit: 28 binaries pre-installed in the base ISO (18 Kodachi core and dashboard, 2 companion tools, 8 KAICS AI).
AI-ready: the 8 KAICS ai-* binaries ship pre-installed; AI workflows and models are enabled on demand.
Maximum compatibility: 23 firmware and microcode packages for WiFi, Ethernet, Bluetooth, GPU, and CPU.
Whether you need a dedicated proxy server for your network or a safe testing environment for Kodachi binaries, Kodachi Terminal Server provides a complete, lightweight solution.