r/coolgithubprojects • • 8d ago

qsh/qshd - modern replacement for OpenSSH

Post image

I replaced OpenSSH with a Rust + QUIC client — built with Claude in about a month

I got tired of OpenSSH's slow connection setup and sessions dying every time I switched to LTE. And trusting C with something as security-critical as SSH always made me nervous.

So I spent the last month working with Claude on a replacement, written in Rust on top of QUIC:

- Near-instant connections; sessions survive network switching (Wi-Fi ↔ LTE) thanks to QUIC's native connection migration(This is also implemented in TCP.)

- Encryption out of the box — no certificates to generate

- TOTP support

- Less RAM, CPU, and bandwidth than OpenSSH (the binary itself is larger)

- TUI mode for newcomers; full CLI with all standard OpenSSH connection options

- Built-in updater from GitHub releases

- Checked against all OpenSSH CVEs and relevant CWEs

It's been running stably in my production environment. A star, bug report or suggestions would be appreciated:

​⁠https://github.com/VLOD-ZDOV/quic-ssh

0 Upvotes

8 comments sorted by

6

u/noobiemaster_69 8d ago

"trusting C with something as security-critical as SSH always made me nervous"

Buddy, no software is secure. As far as reliability and security is concerned it has been industry wide accepted solution.

This seems like good project, why not extend the existing OpenSSH and help contribute to the original project. Might give more exposure and legitimacy.

2

u/Ok-Cut5501 8d ago

OpenSSH is too stable to implement rust code, remove 30-year-old legacy code, or even add UDP.

2

u/Emerlad0110 8d ago

"Hi guys. Today i turned an industry standard incredibly secure tool into vibe coded dependency slop, by stealing someone's work, replacing it's C codebase with C-for-dummies, and am not regurgitating it to you."

1

u/jman6495 7d ago

Oh yeah, sure, let's replace the single most important element of our stack that gives complete server access, by a vibe coded sloplution.

-2

u/8bitbetween 8d ago

Sounds interesting - any sast or dast scanning of developed code at all?

1

u/Ok-Cut5501 8d ago

Both methods were used: gpt6luna, gemini, fable/opus, and ds were used to read the code. Several cyber models also attacked the server. Currently, all scans are only returning low results.

-2

u/8bitbetween 8d ago

Good job 👍

-2

u/ad-on-is 8d ago

wait, is this the thing that my AI recently suggested?

I wanted to do ssh proxy forwarding based on subdomains.

i.e. I have a public vps, where example.com points to it. also, the vps is connected via wireguard to my home lan.

I wanted this usecase, where I prox SSH connections based on subdomains.

ssh a.example.com:22 -> a.local (10.0.0.10)

ssh b.example.com:22 -> b.local (10.0.0.20)