←back to thread

SSH3: Faster and rich secure shell using HTTP/3

(github.com)
532 points tempaccount420 | 3 comments | 27 Sep 25 14:27 UTC | HN request time: 0.606s | source
Show context
kelnos ◴[27 Sep 25 18:50 UTC] No.45398425[source]▶
> Establishing a new session with SSHv2 can take 5 to 7 network round-trip times, which can easily be noticed by the user. SSH3 only needs 3 round-trip times. The keystroke latency in a running session is unchanged.

Bummer. From a user perspective, I don't see the appeal. Connection setup time has never been an annoyance for me.

SSH is battle-tested. This feels risky to trust, even whenever they end up declaring it production-ready.

replies(7): >>45399046 #>>45399565 #>>45399743 #>>45399861 #>>45401100 #>>45401784 #>>45402561 #
1. thethimble ◴[27 Sep 25 20:23 UTC] No.45399046[source]▶
Head-of-line blocking is likely fully addressed by ssh3 where multiplexing several ports/connections over a single physical ssh3 connection should be faster.
replies(1): >>45399329 #
2. john01dav ◴[27 Sep 25 21:09 UTC] No.45399329[source]▶
Calling anything here "physical" is strange and confusing to me. Surely you don't mean the physical layer?
replies(1): >>45400821 #
3. zamadatix ◴[28 Sep 25 00:58 UTC] No.45400821[source]▶
I've seen it a lot with communication protocols for some reason, I guess it's just relatively clear it means "the non virtualized" even though it's clearly a misnomer. E.g. with VRRP a ton of people just say "the physical IP" when talking about the address that's not the VIP, even though the RFC refers to it as "the primary" IP. Arguably "primary IP" is more confusing as to which is being referred to, even though it's more technically accurate.

Of course, maybe there's a perfectly obvious word which can apply to all of those kinds of situations just as clearly without being a misnomer I've just never thought to mention in reply :D.