Osewa – An open-source alternative to SSH and Mosh
dkpk
24 points
19 comments
November 04, 2026
Related Discussions
Found 5 related stories in 127.4ms across 11,645 title embeddings via pgvector HNSW
- OxiSH: SSH Server Written in Rust wofo · 16 pts · August 13, 2026 · 61% similar
- Show HN: OxiSH, a modern, memory-safe SSH server dochtman · 19 pts · August 13, 2026 · 58% similar
- Show HN: Mosh-rs, Mosh rewritten in Rust with scrollback and Windows support Arunjay__ · 12 pts · October 14, 2026 · 53% similar
- OccupySaaS misswaterfairy · 163 pts · November 02, 2026 · 49% similar
- OpenJev ilreb · 595 pts · September 18, 2026 · 49% similar
Discussion Highlights (9 comments)
mellosouls
Tangential feedback: As clever as it might be, the website made me pull back when opening and drilling in on mobile, quite disorienting.
vermon
Aren't ssh and mosh open-source or what does that mean?
yellow_lead
Here's the github: https://github.com/rjyo/osewa every commit has claude as an author (judge as you may) Security: > Where ssh is ahead is age: OpenSSH has decades of audits and osewa has none yet, I think this is most important when concerning remote connections to your computer. though, that doesn't mean we should never improve.
nannal
Finally an open source alternative to ssh
maeln
The limitation of SSH and Mosh are real, and SSH over Quic is not a novel idea but a good one. But SSH is a *highly critical* piece of software. A security issue in SSH is basically like giving the keys to the whole kingdom. In such a critical environment, I highly doubt a slop-coded "SSH but on Quic" will be well received. And you can already do that with Iroh and dumbpipe minus the slop code.
hypfer
Something as essential to security like ssh should probably not be reinvented as AI slop like this for most if not all use-cases.
frumiousirc
One of the main features of mosh is that it keeps local tty state and can do state transfer and update with the remote pty. This lets the user continue to type and see a (local) echo even when transport is lost. A mosh comparison on typing latency benchmark is notably missing and this entire feature goes unmentioned.
markush_
A lot of things here look directionally right, like using QUIC and separating session from connection. However as others said the security implications of this make it almost unusable for production systems. It’s also unclear how often bad connection and roaming is a problem for real world usage. On the session side I think applications like Rex from Superlogical are going to build similar functionality on existing protocols
iamnothere
Why not throw these tokens at finding bugs in mosh rather than vibecoding something that nobody with sense will use? I don’t get it. I usually don’t like to be a drive-by hater on projects that people post here, but a vibecoded SSH is irresponsible.