←back to thread

SSH3: Faster and rich secure shell using HTTP/3

(github.com)
532 points tempaccount420 | 4 comments | 27 Sep 25 14:27 UTC | HN request time: 0.91s | 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 #
s-macke ◴[27 Sep 25 15:57 UTC] No.45396881[source]▶
It is not faster in this sense. However, an SSH connection can have multiple substreams, especially for port forwarding. Over a single classical connection, this can lead to head-of-line blocking, where an issue in one stream slows everything down. QUIC/HTTP3 protocol can solve this.
replies(2): >>45398048 #>>45401658 #
1. inetknght ◴[28 Sep 25 04:00 UTC] No.45401658[source]▶
Fun fact: SSH also supports multiple streams. It's called multiplexing.
replies(3): >>45401898 #>>45402432 #>>45403658 #
2. Aachen ◴[28 Sep 25 05:01 UTC] No.45401898[source]▶
Doesn't it run over a single TCP connection in all cases, unless you manually launch multiple and manually load-balance your clients across is? As in, it won't/can't open a new TCP connection when you open a new connection in the SOCKS proxy or port forward. They'll all share one head-of-line and block each other

Not that I've ever noticed this being an issue (no matter how much we complain, internet here is pretty decent)

Edit: seeing as someone downvoted your hour-old comment just as I was adding this first reply, I guess maybe they 'voted to disagree'... Would be nice if the person would comment. It wasn't me anyway

3. lxgr ◴[28 Sep 25 07:30 UTC] No.45402432[source]▶
Multiple streams at the application level, which can be head-of-line blocked due to all being multiplexed on the same transport layer connection.

The former kind of multiplexing addresses functionality, the latter performance.

4. ◴[28 Sep 25 11:50 UTC] No.45403658[source]▶