Linux Kodachi V9.01 Released — It’s Back!

[BlackwolfOz]

Linux Kodachi V9.01 Released — It’s Back!
Hey folks

Just a quick heads-up for anyone who’s been following Linux Kodachi over the years — after nearly two years of silence, it’s officially been re-spun and revived by Warith!
That means it’s now available again for everyone to download.

Download / Info: https://www.kodachi.cloud/wiki/bina/index.html

Kodachi remains a hardened, privacy-focused Debian-based distro built for users who want strong anonymity without wrestling with complex setups.
It ships with a fully pre-configured security stack: failover VPN routing, Tor integration, DNSCrypt, leak-prevention mechanisms, and anti-forensic protections.
The goal is simple — secure out-of-the-box computing with enough depth for power users who want to dig deeper.

If you’ve been waiting for Kodachi to return, it’s back.

 

[wizardfromoz]

@BlackwolfOz welcome to linux.org.

Given this is Debian-based, it should be in https://www.linux.org/forums/debian-and-derivatives.154/ - I will move it there.

Also, the above is not a Tutorial, so I have removed that banner.

Chris Turner
wizardfromoz

 

[BlackwolfOz]

Okay - thanks for the clarification!
Much appreciated.

 

[BlackwolfOz]

One important point about Kodachi: routing through Kodachi servers is optional, not required. Kodachi is designed so users can bring their own infrastructure and avoid Kodachi nodes completely if that fits their threat model better.

The dashboard supports custom VPN and tunnel configs, including WireGuard, OpenVPN, Shadowsocks, VLESS, VMess, Trojan, V2Ray, Xray, sing-box, Clash/Mihomo, Hysteria2, Mieru, Dante, IPsec/L2TP, OpenConnect, stunnel, ZeroTier, Tailscale, and Tor transports such as obfs4, snowflake, and meek. You can load your own config and route traffic through your own server.

It also includes dashboard support for third-party providers such as ProtonVPN, Mullvad, IVPN, NordVPN, ExpressVPN, Surfshark, PIA, Windscribe, RiseupVPN, and Cloudflare WARP. In those cases, the traffic path is between the user and the selected provider, not Kodachi infrastructure.

So the trust model is not “trust Kodachi servers or do not use Kodachi.” It is much closer to: use Kodachi as the control layer, then choose the route you trust.

On the proprietary parts, I understand the concern. But proprietary does not automatically mean blind trust. Kodachi provides hashes, signatures, public-key verification, inspectable scripts/components where available, and the ability to avoid Kodachi nodes entirely.

Also, I personally see accountability as a strength here. Warith is not hiding behind an anonymous team name. He publishes Kodachi under his real identity, with his name, background, reputation, and public presence attached to it. That does not remove the need for verification, but it does create more accountability than a completely anonymous operator who can disappear at any time.

In the end, Kodachi gives users options: use the parts you trust, replace the parts you do not, and choose the routing path that matches your own threat model.

 

[BlackwolfOz]

Here it is in action
Kodachi 9: WireGuard + Tor Anonymization Walkthrough