Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SSH3: Faster and rich secure shell using HTTP/3

github.com

Post reply on HN
Print view View original

181–190 of 276 posts

Re: SSH3: Faster and rich secure shell using HTTP/3

#181

Post by Dylan16807 »

teddyh wrote: post #146
zdw wrote: post #22

Earlier quoted context omitted.

Same - this feels equivalent of some rando making a repo called "Windows 12" or "Linux 7".

C.f. “JSON5”.

Eh. JSON forfeited version numbers, and if this analogy ran all the way through then we'd be looking at a scenario where SSH is based on HTTP 1 or 2. In that situation calling the HTTP/3 version SSH3 would make a lot of sense.

Re: SSH3: Faster and rich secure shell using HTTP/3

#182

Post by treve »

catlifeonmars wrote: post #63
formerly_proven wrote: post #43

Earlier quoted context omitted.

Easy: hhs instead of ssh (since the even more obvious shh is essentially impossible to google). Stands for, idk, HTTP/3 Hardened Shell or something ("host shell"? sounds like windows)

hss? Http/3 Secure Shell?

Or h3ss, pronounced hess

Re: SSH3: Faster and rich secure shell using HTTP/3

#184

Post by zamadatix »

voxadam wrote: post #177
gdevenyi wrote: post #147

Earlier quoted context omitted.

Sadly this project looks dead.

Is it dead or just mature?

Mature should still be fixing bugs, which something like mosh is bound to always run into. From that perspective, it doesn't seem like it's just mature. There doesn't seem to be a clear all-in-one successor fork taking the reins either. E.g. https://github.com/mobile-shell/mosh/issues/1339, as a random sample.

Re: SSH3: Faster and rich secure shell using HTTP/3

#185

Post by akdor1154 »

psanford wrote: post #19

I do hate the name ssh3. I was glad to see this at the top of the repo: > SSH3 is probably going to change its name. It is still the SSH Connection Protocol (RFC4254) running on top of HTTP/3 Extended connect, but the required changes are heavy and too distant from the philosophy of popular SSH implementations to be considered for integration. The specification draft has already been renamed ("Remote Terminals over H…

Quissh?

Re: SSH3: Faster and rich secure shell using HTTP/3

#186

Post by zamadatix »

john01dav wrote: post #136
thethimble wrote: post #129

Earlier quoted context omitted.

Head-of-line blocking is likely fully addressed by ssh3 where multiplexing several ports/connections over a single physical ssh3 connection should be faster.

Calling anything here "physical" is strange and confusing to me. Surely you don't mean the physical layer?

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.

Re: SSH3: Faster and rich secure shell using HTTP/3

#188

Post by [deleted] »

psanford wrote: post #19

I do hate the name ssh3. I was glad to see this at the top of the repo: > SSH3 is probably going to change its name. It is still the SSH Connection Protocol (RFC4254) running on top of HTTP/3 Extended connect, but the required changes are heavy and too distant from the philosophy of popular SSH implementations to be considered for integration. The specification draft has already been renamed ("Remote Terminals over H…

[deleted]

Re: SSH3: Faster and rich secure shell using HTTP/3

#189

Post by dpflan »

nine_k wrote: post #170
psanford wrote: post #19

I do hate the name ssh3. I was glad to see this at the top of the repo: > SSH3 is probably going to change its name. It is still the SSH Connection Protocol (RFC4254) running on top of HTTP/3 Extended connect, but the required changes are heavy and too distant from the philosophy of popular SSH implementations to be considered for integration. The specification draft has already been renamed ("Remote Terminals over H…

/* This is one proper bikeshedding thread if I ever saw one. */

sshhh ... don't sidetrack the productive comment generation. (also, SSHHH as a possible name)...
Post reply on HN