←back to thread

SSH3: Faster and rich secure shell using HTTP/3

(github.com)
532 points tempaccount420 | 1 comments | 27 Sep 25 14:27 UTC | HN request time: 0.001s | source
Show context
Zambyte ◴[27 Sep 25 15:01 UTC] No.45396281[source]▶
I was skeptical of the claim that it's faster than traditional SSH, but the README specifies that it is faster at establishing a connection, and that active connections are the same speed. That makes a lot of sense and seems like a reasonable claim to make.
replies(9): >>45396495 #>>45396529 #>>45396639 #>>45396881 #>>45400344 #>>45400909 #>>45400915 #>>45403285 #>>45410927 #
notepad0x90 ◴[27 Sep 25 15:35 UTC] No.45396639[source]▶
Although, dollars-to-donuts my bet is that this tool/protocol is much faster than SSH over high-latency links, simply by virtue of using UDP. Not waiting for ack's before sending more data might be a significant boost for things like scp'ing large files from part of the world to the another.
replies(6): >>45396713 #>>45396823 #>>45397014 #>>45397091 #>>45397195 #>>45402450 #
finaard ◴[27 Sep 25 15:52 UTC] No.45396823[source]▶
Not really that relevant - anybody regularly using SSH over high latency links is using SSH+mosh already anyway.
replies(2): >>45397106 #>>45402528 #
1. lxgr ◴[28 Sep 25 07:49 UTC] No.45402528[source]▶
If you believe that, you clearly haven't had to work with mosh in a heavily firewalled environment.

Filtering inbound UDP on one side is usually enough to break mosh, in my experience. Maybe they use better NAT traversal strategies since I last checked, but there's usually no workaround if at least one network admin involved actively blocks it.